Custom moves: UndoMove approach. #517
Closed
AlexeyTrefilov
started this conversation in
General
Replies: 1 comment 3 replies
-
Hello @AlexeyTrefilov, had we been designing this API today, maybe we'd do it differently. But at the time when custom moves were designed many years ago, this seemed like the best approach, and so this is what we have. I don't think we'll be changing this; after all, custom moves are not even public API. But we are discussing a whole new way of doing moves - simpler, faster, more powerful. If and when that shows up, it remains to be seen. For the time being, custom moves is what we have. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
I'm trying to implement quite complicate custom move.
And looks like I should create another move to implement createUndoMove.
And this is a question: why should I do that?
I mean, is it not enough to use something like undoMoveOnGenuineVariables? Why should it be the whole move?
Beta Was this translation helpful? Give feedback.
All reactions