Conversation
LlamaLad7
force-pushed
the
feature/lambda-selectors
branch
2 times, most recently
from
October 1, 2026 20:18
0488cd6 to
6a91e73
Compare
LlamaLad7
force-pushed
the
feature/lambda-selectors
branch
from
October 1, 2026 21:58
6a91e73 to
19d3c02
Compare
This branch has not been deployed
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
1 participant
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.
Full resolution and completion support for lambda selectors, along with some related bugfixes. Commits best consumed individually.
Demo:
lambdaselectors2.mp4
Currently intermediate levels' quantifiers' min values are not checked, reporting this properly would be quite difficult and it is unlikely to be used by anyone anyway. This along with reporting failed quantifier minima in a more user-friendly way is left as future work.