chessfriend/position/src/position.rs

// Eryn Wells <eryn@erynwells.me>

mod captures;
mod make_move;
mod position;
mod unmake_move;

pub use {
    make_move::{MakeMoveError, ValidateMove},
    position::Position,
};
[board] Implement all the bit twiddling to track whether castling is allowed for each player and side of the board 2024-01-08 14:41:54 -08:00			`// Eryn Wells <eryn@erynwells.me>`

[position] Move capture list to a CapturesList struct This one has a custom Display implementation for easier integration with Positon's. 2025-05-27 11:49:33 -07:00			`mod captures;`
[position] Move make_move to its own module: position::make_move Rework sight.rs and add a new module, movement.rs, to calculate piece sight and movement. I discovered during this process that "sight" and "movement" are different because pawns (in particular) can move in ways that don't follow their sight lines. The routines in the movement module account for this, but also pass through to the sight routines for other pieces. 2025-05-18 08:08:47 -07:00			`mod make_move;`
[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			`mod position;`
[position] Move unmake move stuff to an unmake_move module 2025-05-27 11:52:17 -07:00			`mod unmake_move;`
[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
[board] Implement danger squares for the current player This concept comes from [1]. Danger squares are the squares a king cannot move to because it would permit the opposing player to capture the king on their next turn. [1]: https://peterellisjones.com/posts/generating-legal-chess-moves-efficiently/ 2024-01-28 00:25:53 -08:00			`pub use {`
[position] Move make_move to its own module: position::make_move Rework sight.rs and add a new module, movement.rs, to calculate piece sight and movement. I discovered during this process that "sight" and "movement" are different because pawns (in particular) can move in ways that don't follow their sight lines. The routines in the movement module account for this, but also pass through to the sight routines for other pieces. 2025-05-18 08:08:47 -07:00			`make_move::{MakeMoveError, ValidateMove},`
[position] Move castle evaluation code to its own submodule of position Move the tests too. 2025-05-19 16:59:13 -07:00			`position::Position,`
[board] Implement danger squares for the current player This concept comes from [1]. Danger squares are the squares a king cannot move to because it would permit the opposing player to capture the king on their next turn. [1]: https://peterellisjones.com/posts/generating-legal-chess-moves-efficiently/ 2024-01-28 00:25:53 -08:00			`};`