-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Irrefutable Lambda #1283
Irrefutable Lambda #1283
Conversation
Desugar happens after resolving so this should be not applicable |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1283 +/- ##
============================================
- Coverage 83.41% 83.38% -0.04%
- Complexity 4228 4239 +11
============================================
Files 385 385
Lines 12243 12289 +46
Branches 1411 1418 +7
============================================
+ Hits 10213 10247 +34
- Misses 1282 1291 +9
- Partials 748 751 +3 ☔ View full report in Codecov by Sentry. |
How about the interaction with pushing pattern from lambda in pattern matching? i.e.:
becomes
This may require the desugar in tyck rather than just after resolving. |
🤯🤯🤯.... I think it's ok to not implement this feature. It's unreasonably complicated. Pushing lambda was meant to be a simple feature |
This PR fixes #94 by:
Expr.IrrefutableLam
Expr.IrrefutableLam
toExpr.Lambda
TODO:
Expr.Lambda
even if it is a desugar output?