chessfriend/position/src/lib.rs

// Eryn Wells <eryn@erynwells.me>

mod position;

#[macro_use]
mod macros;

pub use chessfriend_board::{fen, PlacePieceError, PlacePieceStrategy};
pub use chessfriend_moves::{GeneratedMove, ValidateMove};
pub use position::Position;

#[macro_use]
pub mod testing;
[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>`

[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;`

[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] Re-export moves::ValidateMove from the position crate 2025-06-07 20:09:51 -07:00			`pub use chessfriend_moves::{GeneratedMove, ValidateMove};`
[board, moves, position] Move make_move routines to moves crate Declare a MakeMove trait and export it from chessfriend_moves. Declare a BoardProvider trait that both Board and Position implement. Implement the MakeMove trait for all types that implement BoardProvider, and move all the move making code to the moves crate. This change makes it possible to make moves directly on a Board, rather than requiring a Position. The indirection of declaring and implementing the trait in the moves crate is required because chessfriend_board is a dependency of chessfriend_moves. So, it would be a layering violation for Board to implement make_move() directly. The board crate cannot link the moves crate because that would introduce a circular dependency. 2025-05-31 19:01:20 -07:00			`pub use position::Position;`
[board, moves, position] Make the Peter Ellis Jones gotcha unit tests work Move this file over to position/tests. That makes it an integration test, technically. Update it to comply with the current API conventions. This is a pretty radical change from when I first wrote these! In the process of running these tests, I found a bug in my PawnMoveGenerator where it was generating the origin squares for en passant captures incorrectly. Fix those bugs and write two new tests to exercise those code paths. One of the test_board! variants was setting .active_color instead of using the setter. This is a build failure. Fix it. Move the assert_move_list! macro to the moves crate. This is a more natural home for it. Additionally, add assert_move_list_contains! and assert_move_list_does_not_contain! to generate assertions that a collection of moves (anything that implements .contains()) has or doesn't have a set of moves. Also remove formatted_move_list!, which is no longer used. All that done, make the tests pass! 2025-06-06 21:45:07 -07:00
			`#[macro_use]`
			`pub mod testing;`