chessfriend/board/src
Eryn Wells f47654cc98 [board] Trying out a new naming convention in the check methods
I've been bothered by certain instances where the color has already been unwrapped
from an Option<Color> but a subsequent call takes an Option, so you have to rewrap
it to call the method. I might be overthinking this…

For the Board::*_color_is_in_check set of methods, try out this naming convention:

active_color_is_in_check()
: Operates directly on the Board's active color, no unwrapping required
color_is_in_check()
: Takes an Option<Color> and unwraps it with the active color if None is given
unwrapped_color_is_in_check()
: Takes a Color and operates on it. This method is called by the two above, but
is also public.
2025-06-01 19:07:58 -07:00
..
castle [board, moves, position] Implement KingMoveGenerator 2025-05-26 23:37:33 -07:00
piece_sets [board] Implement iter() on board 2025-06-01 17:28:47 -07:00
board.rs [board] Implement iter() on board 2025-06-01 17:28:47 -07:00
board_provider.rs [board, moves, position] Move make_move routines to moves crate 2025-05-31 19:04:21 -07:00
castle.rs [board, moves, position] Implement KingMoveGenerator 2025-05-26 23:37:33 -07:00
check.rs [board] Trying out a new naming convention in the check methods 2025-06-01 19:07:58 -07:00
display.rs [board] Add an option to display a board with ASCII characters 2025-05-23 09:53:59 -07:00
en_passant.rs Move a whole bunch of stuff to the new chessfriend_board package 2024-04-25 13:28:24 -07:00
fen.rs [board, core, moves, position] Implement castling 2025-05-19 16:50:30 -07:00
lib.rs [board, moves, position] Move make_move routines to moves crate 2025-05-31 19:04:21 -07:00
macros.rs WIP 2025-05-08 17:37:51 -07:00
movement.rs [board, moves, position] Implement KingMoveGenerator 2025-05-26 23:37:33 -07:00
piece_sets.rs [board] Implement iter() on board 2025-06-01 17:28:47 -07:00
sight.rs [board, moves, position] Implement KingMoveGenerator 2025-05-26 23:37:33 -07:00