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 involving macros, resetLocalAttrs, and singleton types #7516
Comments
Imported From: https://issues.scala-lang.org/browse/SI-7516?orig=1 |
@paulp said: |
@retronym said: I think I'll revert the fix altogether on 2.10.x, and refine it on master to only use the stable type for the named arguments if needed to conform to the formal parameter type. The real bug is the resetAttrs concept. |
@gkossakowski said: |
@retronym said (edited on May 25, 2013 5:12:31 PM UTC): I'm exploring ways that macros can avoid the need to use resetAttrs, e.g. if they just need to splice a tree into a new context, we just need to expose See also: |
@paulp said: The compiler as it is will never be robust. As long as methods with names like "resetFoo" are piled on top of the problem rather than doing something about the root cause, this will never change. |
@gkossakowski said: I agree that trying to reset mutable state in case of ad-hoc caching mechanisms we have in the compiler is not a good idea. I just wanted to know what breaks exactly in this particular case. Thanks to both Jason and Paul. |
@paulp said: |
@retronym said: |
@harrah said: |
The following REPL transcript works in 2.10.1, but not 2.10.2-RC1:
The code compiles in 2.10.2-RC1 when one of:
The text was updated successfully, but these errors were encountered: