Repository navigation
grow the endgame's table a piece at a time - #386
Merged
Merged
Conversation
A table that doubled moved every entry within the store that filled it, so a solve stopped by a time limit could overrun it by the whole move, which grows with the table. Past a megabyte, the bigger table is now made empty, and the old entries are moved into it, a piece at each store; a position read or stored meanwhile is moved first, so it is only ever in one of the two tables. A memory limit does not count the old table while it waits to be freed: the growing took its room with it held, so a solve stops on the limit as if the table had grown at once. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.