Translating "zero" constructor of Nat to "0" literal #184
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've found @uncle-betty's workaround for natural pattern matching at #117 quite useful. To be more precise, this one, when we make an equivalent version where we only pattern-match for zero:
However, this is not supported anymore per #154. I consider it to be useful; so I've rewritten
Function.hs
so that it always rewritesAgda.Builtin.Nat.Nat.zero
to a0
literal. Pattern matching tosuc
would still be rejected.I don't know whether it would require a broader consensus; but I think we wouldn't lose anything by adding this feature. Thanks in advance for looking at it:)