Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's arguable. The motivation for the rule, and especially the name of the rule, suggest the pawn is not all the way there yet.


In what sense is the pawn not all the way there? It occupies the square, prevents any other piece from occupying the square, can deliver check or checkmate from the square, and can be captured on the square.


The OP refers to the fact that “en passant” is french for “in passing”, so the move sort-of refers to the idea that the pawn takes the other pawn while it is passing through the third or seventh row, as if the capture starts while the previous move still is in progress.

Also, the pawn can’t deliver checkmate, can it, if it can be taken en passant? It probably is possible to construct a position where taking en passant would bring the king into check in another way, but in those cases, the en passant move isn’t possible.


> Also, the pawn can’t deliver checkmate, can it, if it can be taken en passant? It probably is possible to construct a position where taking en passant would bring the king into check in another way, but in those cases, the en passant move isn’t possible.

I believe I've managed to construct a situation where this is the case. The key is that the pawn that would be able to take en passant is being pinned (e.g. by a queen or rook) with the king directly behind it, such that the pawn cannot perform any captures. Then, you just need to make sure all of the squares adjacent to the king are threatened, and finally actually put the king into check via a pawn advancing two squares.

Technically, the c4 pawn cannot be taken en passant (i.e. this is an illegal move) because it would expose the black king to a different check. But I think this is in the spirit of your question.

Contrived game (which you should be able to import into https://www.chess.com/analysis or https://lichess.org/analysis):

1. e4 d6 2. e5 Kd7 3. h4 Kc6 4. Rh3 d5 5. a4 d4 6. Raa3 Kc5 7. Rhg3 Kb4 8. Rg4 Qe8 9. Rag3 Qd8 10. Rg5 Kxa4 11. Rd3 Kb5 12. Ra3+ Kb6 13. d3 Kb5 14. Be2 Kc5 15. Bg4 Qd5 16. Rb3 Qe4+ 17. Ne2 Qxd3 18. Qxd3 Kd5 19. Rb6 a6 20. Nbc3+ Kc5 21. Na4+ Kd5 22. c4#

Or, if you just want to see the end state: blob:https://www.chess.com/20486c7e-a582-41ef-9f1a-bb6fdea2ca36 (seems to work in Chrome, not in Firefox)

(also: https://lichess.org/editor/rnb2bnr/1pp1pppp/pR6/3kP1R1/N1Pp2...)


Idioms do not have to be interpreted as literal, so I don't understand why anyone would think this. As I understand it:

https://lichess.org/editor/rnbqkbnr/pp3ppp/8/3pp3/2pPP3/4K3/...

the King is never in check, for the purposes of the game. The piece removed isn't in the destination square.


It's because pawns used to be able to move only one square. En passant was created when they were allowed to move two squares, sort of pretending that it only moved one square and is why you can only do it immediately after the first pawn move, kind of where the pawn "should" be.


In the sense that a pawn that's in the perfect position can strike while it is "passing", but if that doesn't happen then it finishes the move and it's too late, the opportunity is gone forever.


Sure, but we don't have the same rule for a rook or bishop "passing" through a square where a pawn could strike it in passing.

It's just it's own unique rule, born from a period of transition between pawns only being able to take one step and being able to take two.


Though castling does take all kinds of strikes in passing into account for the king.


True. It's as if any piece could kill the king in transition.

And yet other pieces can't kill that pawn in passing. Only another pawn.

We shouldn't try to find too much logic.


Clearly there's some Heisenberg uncertainty principle where the pawn occupies both the third (or sixth) and fourth (or fifth) rank, in a kind of superposition that only an opponent pawn situated in a certain position would be able to observe.


I think the logic is based on pragmatism. A different piece has a chance of capturing the pawn later, but a pawn would never be able to since it can't go backwards.


That's a good way to look at it.

Practically, game engines model this with an extra state variable in the tree indicating the capturable square.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: