Duplicate Position/pieces about chessproblem HOT 2 OPEN

I would like to go with the latter option of eliminating the Position from Piece as it is easy to map with real objects and having Board. Position class is mainly for converting the problem statement notation to rows/columns and vice versa. May be we implement like ChessBoard -> Position -> Piece has a relationship.

from chessproblem.

Madhusudhan Srikkanth I have not looked at his code but I do agree that functionality or and state must not be duplicated.

But if it I a choice between storing position in a board or in pieces, then they are both not equivalent. Storing positions of pieces on a board object makes more sense because then pieces will have a single object that they can query to say for example get all valid positions for a piece. Doing this with positions stored in a piece would be messy code. Always remember the S in SOLID principles which stands for Single Responsibility Principle for each class.

from chessproblem.