-
-
Notifications
You must be signed in to change notification settings - Fork 655
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
Regression wrt complex type positions #11431
Comments
I'm not sure it's the right fix but it now gives me proper position for my refactoring. Reopening so @Simn can give a deep look maybe. |
It might be better if |
How exactly do you create these |
Simn
added a commit
that referenced
this issue
Dec 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In current Haxe, the position is now part of the complex type. However when creating complex type with macros we don't always have this position set, in which case it will be set to
null_pos
. But the problem is that if the type is not found, Haxe compiler will simply printType not found : Name
to the output without any position context, making it very hard to debug...I can easily hit into this error by refactoring some code, without much macros involved so I think that's quite a significant issue.
The text was updated successfully, but these errors were encountered: