4 ms·

I think this would help a lot. It would also help to check whether the code mentioned in an issue that triggers a crash is equivalent to the code you have. Eve

I think this would help a lot. It would also help to check whether the code mentioned in an issue that triggers a crash is equivalent to the code you have. 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.

harveywi 10y ago
Here is a new one that I reported to scala-internals today: https://groups.google.com/forum/#!topic/scala-internals/w4HGp4_QQwk https://groups.google.com/forum/#!topic/scala-internals/w4HG...
- premium-concern 10y ago
  Great, thanks!
  - harveywi 10y ago
    I hit two bugs today. Both were produced during major global refactoring. I did not have time to catalogue the reproduction steps or anything, so I have no right to complain! 1. https://issues.scala-lang.org/browse/SI-9281 https://issues.scala-lang.org/browse/SI-9281 2. https://issues.scala-lang.org/browse/SI-8322 https://issues.scala-lang.org/browse/SI-8322
    - harveywi 10y ago
      And another one today: https://issues.scala-lang.org/browse/SI-9222 https://issues.scala-lang.org/browse/SI-9222
      - premium-concern 10y ago
        Thanks! What the hell are you doing that you experience issues this often? :-)
        harveywi 10y ago
        I'm working on extending this ([1]) to contravariant functors while making the whole thing polytypic and typesafe (so I can abstract over type products and coproducts, among other things). My stuff will be open-sourced next year sometime at the latest. I think it's a combination of feature interactions and frequent refactoring during development that is a source for a lot of stuff that is not nice to the compiler. 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/main/scala https://github.com/jdegoes/scalaworld-2015/tree/master/src/m...
harveywi 10y ago
I just bumped into SI-1503 [1] and SI-7714 [2]. Fortunately I was able to work around those and keep plugging away. [1] https://issues.scala-lang.org/browse/SI-1503 https://issues.scala-lang.org/browse/SI-1503 [2] https://issues.scala-lang.org/browse/SI-7714 https://issues.scala-lang.org/browse/SI-7714
- premium-concern 10y ago
  Thanks! SI-1503 should warn in 2.12, additional progress might happen in https://github.com/scala/scala/pull/5310 https://github.com/scala/scala/pull/5310.

harveywi 10y ago

Here is a new one that I reported to scala-internals today: https://groups.google.com/forum/#!topic/scala-internals/w4HGp4_QQwk https://groups.google.com/forum/#!topic/scala-internals/w4HG...

premium-concern 10y ago
Great, thanks!
- harveywi 10y ago
  I hit two bugs today. Both were produced during major global refactoring. I did not have time to catalogue the reproduction steps or anything, so I have no right to complain! 1. https://issues.scala-lang.org/browse/SI-9281 https://issues.scala-lang.org/browse/SI-9281 2. https://issues.scala-lang.org/browse/SI-8322 https://issues.scala-lang.org/browse/SI-8322
  - harveywi 10y ago
    And another one today: https://issues.scala-lang.org/browse/SI-9222 https://issues.scala-lang.org/browse/SI-9222
    - premium-concern 10y ago
      Thanks! What the hell are you doing that you experience issues this often? :-)
      - harveywi 10y ago
        I'm working on extending this ([1]) to contravariant functors while making the whole thing polytypic and typesafe (so I can abstract over type products and coproducts, among other things). My stuff will be open-sourced next year sometime at the latest. I think it's a combination of feature interactions and frequent refactoring during development that is a source for a lot of stuff that is not nice to the compiler. 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/main/scala https://github.com/jdegoes/scalaworld-2015/tree/master/src/m...

harveywi 10y ago

I just bumped into SI-1503 [1] and SI-7714 [2]. Fortunately I was able to work around those and keep plugging away. [1] https://issues.scala-lang.org/browse/SI-1503 https://issues.scala-lang.org/browse/SI-1503 [2] https://issues.scala-lang.org/browse/SI-7714 https://issues.scala-lang.org/browse/SI-7714

premium-concern 10y ago
Thanks! SI-1503 should warn in 2.12, additional progress might happen in https://github.com/scala/scala/pull/5310 https://github.com/scala/scala/pull/5310.