Even if you can't publish your code, it might help to say "I'm seeing the same error, but I'm using X unlike the exmaple code that uses Y".
This will make sure that people who fix a bug will cover both causes with a test.
Even if you can't publish your code, it might help to say "I'm seeing the same error, but I'm using X unlike the exmaple code that uses Y".
This will make sure that people who fix a bug will cover both causes with a test.
SI-1503 should warn in 2.12, additional progress might happen in https://github.com/scala/scala/pull/5310.
edit: The extension to [1] is actually pretty benign and the compiler does well with it. The part that puts a big load on the compiler is that it is used as an interpreter for a popular, yet complicated, visualization DSL. The compiler, especially the typechecker, has to do a huge amount of work.
[1] https://github.com/jdegoes/scalaworld-2015/tree/master/src/m...