Raise compile errors on relevant type node#1149
Merged
Merged
Conversation
jwoertink
approved these changes
Apr 29, 2026
Member
jwoertink
left a comment
There was a problem hiding this comment.
You know, I've never really understood what this does 🤔 Does it just make the stack trace contain a better set of line numbers or something? Should all compile-time exceptions always raised on the type node when the error is based around a specific node?
Contributor
Author
|
Before: After: Basically points to the exact node causing the error. |
Contributor
Author
|
Before: After: The pointer points to the |
Member
|
ooohh! Ok, that's awesome. I never realized that. Thanks for explaining. |
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
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.
No description provided.