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.

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

fix: check pinning status in Uchifuzume detection #8

Merged
merged 1 commit into from
Feb 25, 2017
Merged

Conversation

nozaq
Copy link
Owner

@nozaq nozaq commented Feb 25, 2017

Previously, Uchifuzume was not detected when there is any piece
attacking the dropped pawn even if it was pinned.

This commit checks if pieces attacking the dropped pawn are pinned or
not so that Uchifuzume should be detected if all of them are pinned.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 95.916% when pulling b004f1f on uchifuzume-fix into 605cbe0 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 95.916% when pulling b004f1f on uchifuzume-fix into 605cbe0 on master.

Previously, Uchifuzume was not detected when there is any piece
attacking the dropped pawn even if it was pinned.

This commit checks if pieces attacking the dropped pawn are pinned or
not so that Uchifuzume should be detected if all of them are pinned.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.05%) to 95.975% when pulling 4d33c20 on uchifuzume-fix into 605cbe0 on master.

@nozaq nozaq merged commit bf72dae into master Feb 25, 2017
@nozaq nozaq deleted the uchifuzume-fix branch February 25, 2017 09:04
nozaq added a commit that referenced this pull request Jun 3, 2018
Previously, Uchifuzume was not detected when there is any piece
attacking the dropped pawn even if it was pinned.

This commit checks if pieces attacking the dropped pawn are pinned or
not so that Uchifuzume should be detected if all of them are pinned.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants