-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Crash in macros during separate compilation #7322
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
Comments
I'll bet you can reproduce that with a handwritten |
Could be, so far I haven't had any luck with it. |
My reasoning behind blaming mirrors is that the error message says "assertion failed: position not set" and the knowledge that |
You were right @milessabin, nothing to do with the mirrors. I've updated the initial post with a better-minimized example. |
Doesn't reproduce anymore. We should add a regression test when #7342 is fixed. |
This Inlined node not was added as part of a fix for issue scala#3898. It was an ad-hoc patch that ended up causing more issues than fixes and therfore is removed.
This Inlined node not was added as part of a fix for issue scala#3898. It was an ad-hoc patch that ended up causing more issues than fixes and therfore is removed.
Macros1.scala:
Macros2.scala:
Compile them separately, e.g.:
You will get:
Crash
If you put the contents of
Macros1.scala
inMacros2.scala
and compile only the latter, it will compile.The text was updated successfully, but these errors were encountered: