For SAN, don't over-disambiguate moves #29
Description
Right now for all notation we specify the piece type, the rank/file of the original space and the rank/file of the destination space, whether it was a capture, promotion, en-passant, or castling. Some of this information is redundant given the previous board state. For example, if two rooks can reach the same space and one moves there, It is common to only specify the rank or file of the rook that moved (I forget which is a higher priority). If only one piece of that type can reach the space, neither the rank or file are specified.
This is how standard algebraic notation works and should probably be followed