-
Notifications
You must be signed in to change notification settings - Fork 939
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
Scala compiler crash when compiling a setting #1150
Comments
@jsuereth: I assigned it to sbt 0.13.2 because it's a regression. Feel free to reconsider. It's most likely a bug in macro code. |
Yes. I'm still fighting the madness of fragmented settings :). Might have to delay the release one more week as I get a handle on things anyway, but this is still correctly assigned. |
// cc @retronym who might have some insights I haven't gotten around to dig deeper into it, yet. |
I'm actually surprised that: (sourceDirectory in Compile).apply(base => base / "assets" ** "_*.styl").value.get worked beforehand. @gkossakowski's suggestion to rewrite the build as: val foo = ((sourceDirectory in Compile).value / "assets" ** "_*.styl").get would be the typical way to express this. I'll trace out the crash in any case. |
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
@retronym @gkossakowski It seems another mole poped out of its hole, this one in our own build:
I may need to revert this just to continue fixing other Ivy issues. |
Appears to be this syntax: loadedTestFrameworks := testFrameworks.value.flatMap(f => f.create(testLoader.value, streams.value.log).map( x => (f,x)).toIterable).toMap, |
@jsuereth: yes, please go ahead and revert. We'll investigate the problem shortly. |
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
The qualifier of the `.value` call may contain `DefTree`s (e.g. vals, defs) or `Function` trees. When we snip them out of the tree and graft them into a new context, we must also call `changeOwner`, so that the symbol owner structure and the tree structure are coherent. Failure to do so resulted in a crash in the compiler backend. Fixes sbt#1150
Consider the following
build.sbt
definition:It crashes with sbt 0.13.2-{M1, M2} with:
It worked with sbt 0.13.1 so this a regression.
The text was updated successfully, but these errors were encountered: