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
..
src	[board] Trying out a new naming convention in the check methods	2025-06-01 19:07:58 -07:00
Cargo.toml	[board, core] Update error types to use thiserror::Error	2025-05-19 08:34:32 -07:00