No description
Find a file
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
bitboard [bitboard, board, core, moves] Implement SliderMoveGenerator 2025-05-26 17:41:43 -07:00
board [board] Trying out a new naming convention in the check methods 2025-06-01 19:07:58 -07:00
core [bitboard, board, core, moves] Implement SliderMoveGenerator 2025-05-26 17:41:43 -07:00
doc Move Notes and ChessPieces docs to a doc directory 2024-01-22 19:27:08 -08:00
explorer [explorer, moves, position] Implement bespoke make_move and unmake_move methods on Position 2025-06-01 19:02:53 -07:00
moves [moves] Implement From<GeneratedMove> for Move 2025-06-01 19:03:28 -07:00
position [explorer, moves, position] Implement bespoke make_move and unmake_move methods on Position 2025-06-01 19:02:53 -07:00
.gitignore Ignore the target/ directory 2023-12-19 11:13:41 -08:00
Cargo.lock [explorer, moves, core] Improve error handling in explorer 2025-05-19 14:18:31 -07:00
Cargo.toml Empty board package 2024-04-25 09:32:27 -07:00
ChessFriend.code-workspace Visual Studio Code workspace 2024-02-11 10:22:33 -07:00
Makefile WIP 2025-05-08 17:37:59 -07:00