-
Notifications
You must be signed in to change notification settings - Fork 26
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
"bound at" information isn't very precise. #36
Comments
Why isn't it correct? Edit: Ah, I suppose you should be required to use a'.. wonder why that happened... |
Something very wrong... even code like
will pass. |
It's a simple bug. I just forgot to emit |
Fixed. |
|
No, it gives this for me:
|
Indeed.. don't know why it didn't install to the right place.. |
the first location isn't good. |
First location? |
this one ---> |
Yeah unfortunately the locations aren't very precise in the column... patterns don't carry location information IIRC. I might be able to fix that at some point but it means reworking the AST a bit. |
This solves #36. FIXME: * Lots of locations are still not accurate, esp. in desugarer; * Pattern context might not be good enough (or not added properly);
This solves #36. FIXME: * Lots of locations are still not accurate, esp. in desugarer; * Pattern context might not be good enough (or not added properly);
This solves #36. FIXME: * Lots of locations are still not accurate, esp. in desugarer; * Pattern context might not be good enough (or not added properly);
This solves #36. FIXME: * Lots of locations are still not accurate, esp. in desugarer; * Pattern context might not be good enough (or not added properly);
This solves #36. FIXME: * Lots of locations are still not accurate, esp. in desugarer; * Pattern context might not be good enough (or not added properly);
This program doesn't look correct but typechecks:
The text was updated successfully, but these errors were encountered: