-
Notifications
You must be signed in to change notification settings - Fork 21
Crash in constructors phase involving macros #8425
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
Imported From: https://issues.scala-lang.org/browse/SI-8425?orig=1 |
@gkossakowski said: |
@xeno-by said: |
@gkossakowski said: |
@retronym said: |
@retronym said:
|
@retronym said (edited on Mar 17, 2014 10:57:25 PM UTC):
|
@retronym said (edited on Mar 17, 2014 11:24:20 PM UTC):
Now we helpfully add a second '$' in addition to the one added by Spire. The '$$' looks like an expanded name (ie, one that has the FQCN prepended to make it unique when we are forced to make something Scala-private JVM public). The // The constructor parameter corresponding to an accessor
def parameter(acc: Symbol): Symbol = parameterNamed(acc.unexpandedName.getterName) That doesn't exist in the list of constructor parameters. The error message is confusing because the same un-expansion is happening somewhere in I suggest that fresh-name generation should not add a '$' if the user provided prefix already ends in '$'. |
@xeno-by said (edited on Mar 17, 2014 11:16:23 PM UTC): |
@retronym said (edited on Mar 17, 2014 11:21:37 PM UTC): Nor being built: https://scala-webapps.epfl.ch/jenkins/view/scala-release-2.11.x/job/scala-release-2.11.x/ Could you submit a PR and email Adriaan to give him the option to include a fix. I'd be happy enough with a unit test to show that |
@xeno-by said (edited on Mar 17, 2014 11:29:02 PM UTC): upd. I'd like to emphasize that #8387 is very important for macros, as it creates a major flaw in a frequently used quasiquote pattern, which we won't be able to easily fix later on, because people will naturally grow dependent on its current behavior. |
@gkossakowski said: Is there a work-around present for this issue that users can employ? What about striping additional dollar in case it got returned by {{freshName}}? Let's step back from the excitement and look at the landscape: it's a regression that has been detected in tests of just one project using an experimental feature. If there's a work-around then I'd like to demote this to Major and I don't think we should block the release. |
@xeno-by said: |
@adriaanm said: |
@retronym said: |
@retronym said: |
@gkossakowski said: |
@adriaanm said: |
@retronym said: |
@gkossakowski said: |
@adriaanm said: |
@paulp said (edited on Mar 18, 2014 2:35:06 AM UTC): |
When compiling
tests
subproject ofspire
we get a compiler crash in constructors phase:At the moment reproduction is a bit hard because it requires a dbuild configuration.
The text was updated successfully, but these errors were encountered: