Linking errors on Scala 2.11 if an `object` is named `class`
See original GitHub issueThe following code works fine on Scala 2.12, but does not link on Scala 2.11:
object `class` {
def foo() = {
println("Hello, World!")
}
}
`class`.foo()
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Trying to cross compile a project to Scala 2.11 fails with "error ...
sbt - Trying to cross compile a project to Scala 2.11 fails with "error while loading Object, Missing dependency 'object scala in compiler...
Read more >Linking Errors - Scala.js
If the Referring to non-existent line mentions a class from your own codebase, you are probably facing an incremental compilation issue.
Read more >Scala ide can't compile or run a project with one object and ...
When I renamed the scala/ dir to scala-2.11/ and re-ran sbt eclipse everything worked. No Exceptions and the error messages in scala-ide went...
Read more >IntelliJ IDEA - Troubleshoot common Scala issues - JetBrains
Check the following answers on most common scala/sbt questions that can help you solve compiler, performance or code highlighting issues you might come ......
Read more >The Scala Plugin - Gradle User Manual
This dependency will then be used on compile and runtime class paths. It will also be used to get hold of the Scala...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We don’t really do backlog for compiler bugs. 😉 Either there is a very good reason not to fix something, and we close it as won’t fix, or we fix it ASAP. And for the former case, there are exceptionally few issues. Overall there are 20 won’t-fix bugs that are not internal nor 0.6.x-only, and not all of those are compiler bugs. And with this issue fixed, we are back to 0 open compiler bugs.
Fixed in 36a92e3ff81789c57a6b82a866dcc0b1bc1b4653