chessfriend/position/src/lib.rs

// Eryn Wells <eryn@erynwells.me>

mod move_record;
mod position;

#[macro_use]
mod macros;

#[cfg(test)]
#[macro_use]
mod testing;

pub use chessfriend_board::{fen, PlacePieceError, PlacePieceStrategy};
pub use position::{Position, ValidateMove};
[board] Some test helpers that produce Squares from algebraic notiation and assert their validity 2023-12-28 12:08:37 -07:00			`// Eryn Wells <eryn@erynwells.me>`

[position] Add move tracking to Position Create a new MoveRecord struct that tracks the move (aka ply) and irreversible board properties. This should make it easier to unmake moves in the future. 2025-05-23 10:00:20 -07:00			`mod move_record;`
[board] Cave to pressure and implement fmt::Display for Position It prints a nice diagram! Now I can make the position module private. 2024-01-19 18:11:27 -08:00			`mod position;`
[board] Reorganize bitboard and position modules and export some symbols from the crate Move position.rs to the position module and create a mod.rs. Do the same for bitboard.rs in the bitboard modules. Export Color, Piece, Position, and Square and use crate::Thing directly instead of referring to the symbol in the nested modules. 2023-12-26 11:25:27 -07:00
[core,board] Move board::piece to core Break up types in core into finer grained modules. Update all the imports. 2024-01-24 17:08:27 -08:00			`#[macro_use]`
			`mod macros;`

Replace uses of types in r#move with types from the moves package types 2024-02-25 09:52:40 -08:00			`#[cfg(test)]`
Add an assert_move_list! macro to help with verifying move lists 2024-01-28 15:47:32 -08:00			`#[macro_use]`
Move position::tests → testing Expand information printed in assert_move_list 2024-02-25 09:20:45 -08:00			`mod testing;`
Add an assert_move_list! macro to help with verifying move lists 2024-01-28 15:47:32 -08:00
[board, core, moves, position] Implement castling Implement a new method on Position that evaluates whether the active color can castle on a given wing of the board. Then, implement making a castling move in the position. Make a new Wing enum in the core crate to specify kingside or queenside. Replace the Castle enum from the board crate with this one. This caused a lot of churn... Along the way fix a bunch of tests. Note: there's still no way to actually make a castling move in explorer. 2025-05-19 16:50:30 -07:00			`pub use chessfriend_board::{fen, PlacePieceError, PlacePieceStrategy};`
[position] Remove CastleEvaluationError from this crate It moved to board. 2025-05-23 09:58:29 -07:00			`pub use position::{Position, ValidateMove};`