Eryn Wells 1d7dada987 [bitboard, core, position] Implement proper castle move generation ... Add a field to MoveSet called special that flags special moves that should be generated in the iter() method. This field is a u8. It only tracks castles in the first and second bits (kingside and queenside, respectively). The move iterator chains two maps over Option<()> that produce the kingside and queenside castle moves. With that done, finish the implementation of Position::player_can_castle by adding checks for whether the squares between the rook and king are clear, and that the king would not pass through a check. This is done with BitBoards! Finally, implement some logic in PositionBuilder that updates the position's castling flags based on the positions of king and rooks. Supporting changes: - Add Color:ALL and iterate on that slice - Add Castle::ALL and iterator on that slice - Add a CastlingParameters struct that contains BitBoard properties that describe squares that should be clear of pieces and squares that should not be attacked.		2024-01-29 14:46:41 -08:00
..
src	[bitboard, core, position] Implement proper castle move generation	2024-01-29 14:46:41 -08:00
Cargo.toml	[core] Rename (once again) chess_core → chessfriend_core	2024-01-24 08:48:19 -08:00