Remove recursion tracking from TacticState #1453
Merged
Conversation
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
pepeiborra
approved these changes
Feb 27, 2021
Collaborator
pepeiborra
left a comment
pepeiborra
left a comment
There was a problem hiding this comment.
I approve the generic lenses
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As a followup to #1449, this PR removes the remnants of data that should be in the tactic extract, but was stuck in the state. The core of it is a weird combinator
peekthat @TOTBWF came up with.Also, it was becoming tiresome to pack and unpack
Synthesizeds all the time. So I joined the century of the fruitbat and am now using lenses.