Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Some errors are Unplaced #422

Open
jimbxb opened this issue Nov 14, 2023 · 1 comment
Open

Some errors are Unplaced #422

jimbxb opened this issue Nov 14, 2023 · 1 comment

Comments

@jimbxb
Copy link
Collaborator

jimbxb commented Nov 14, 2023

Some errors are reported without a position. An example can be found in the issue below.

While an ideal patch would be to always have an error reported with a location, that's not always possible. Perhaps, for those cases, we can leverage the current module in the compiler, and report that location as a fallback.

On the lack of location, I believe it should always be possible to get a file-location, which would be nice to have as a fallback when we don't have a location for an error.

Originally posted by @jimbxb in #418 (comment)
@pschachte
Copy link
Owner

The problem is that a fair amount of code is automatically generated in such a way that there is no sensible source location to attach. I don't think we can always ensure that there is a sensible source location for every statement or expression.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pschachte @jimbxb