Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Optimize knightAttacks function after implementing move generation #86

Closed
coderabbitai bot opened this issue Oct 5, 2024 · 0 comments · May be fixed by #82
Closed

Optimize knightAttacks function after implementing move generation #86

coderabbitai bot opened this issue Oct 5, 2024 · 0 comments · May be fixed by #82
Assignees
@Dannyj1

Comments

@coderabbitai
Copy link

coderabbitai bot commented Oct 5, 2024 •
edited by Dannyj1
Loading

As per this comment in PR #82, we need to optimize the knightAttacks function using a lookup table after the move generation is completed. Requested by @Dannyj1.
@Dannyj1 Dannyj1 changed the title Optimize knightAttacks function after move generation Optimize knightAttacks function after implementing move generation Oct 5, 2024
@Dannyj1 Dannyj1 linked a pull request Oct 5, 2024 that will close this issue
Zagreus 6.0 - Rewrite from Scratch #82
Draft
@Dannyj1 Dannyj1 moved this from Todo to Done in Zagreus v6.0 (Rewrite) Oct 11, 2024
@Dannyj1 Dannyj1 closed this as completed by moving to Done in Zagreus v6.0 (Rewrite) Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Dannyj1 Dannyj1

Labels
None yet
Projects
Zagreus v6.0 (Rewrite)
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Zagreus 6.0 - Rewrite from Scratch Dannyj1/Zagreus
1 participant
@Dannyj1