Improve error messages in DefRecursionCheck, Eval example #1046
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.
I wanted to try implementing cats.Eval now that we have polymorphic recursion #1041 .
I couldn't see a way to do it without a poor version of the fuel pattern: promise up front how many recursions you would do at most.
But along the way, I noticed that we are only returning one error message from any branch in the code in DefRecursionCheck, so I implemented a version of the idea in #1044 which allowed me to see all the error messages at once (when they are on parts of the code I was already traversing).