bug
bug copied to clipboard
scala
Scala 2 bug reports only. Please, no questions — proper bug reports only.
```scala package com.middlewareman trait Component case class Event(component: Component) class Owner { object Timestamp extends Component { val state = System.currentTimeMillis() def unapply(name: Timestamp.type) = Some(name.state) } val handler: PartialFunction[Event,...
It took long to minimize :cry: Here is the code that demonstrates two bugs: an error and a compiler crash (see the comments at the end). ```scala package DFiant object...
It doesn't seem possible to use `(=> A) => B` in contexts requiring `A => B`: ```scala scala> def log(a: => Any): Unit = println(a) log: (a: => Any)Unit scala>...
```scala package ws private[ws] trait Foo private[ws] object Test { class Bar { def apply(f: Foo) = ??? } } ``` This leads to: «method apply in class Bar references...
WIP: https://github.com/retronym/scala/compare/topic;diverging-explain?expand=1 example: ``` -starting with method tc in class CompilerHang +starting with method tc in class CompilerHang. + CompilerHang.this.breakage[F] + CompilerHang.this.tc[M] + CompilerHang.this.tc[M] ``` ``` [error] /Users/jason/code/shapeless/examples/src/main/scala/shapeless/examples/ordering.scala:58: diverging implicit...
It would be nice if `-Xlint` also verified that an element annotated `unused` is in fact unused. Currently it's just an exemption from the unused warning. Probably it's not necessary...
Compiling one file in breeze leads to the following crash in specialization. It's enough to compile `math/src/main/scala/breeze/signal/support/CanConvolve.scala` after a full build. Reproduced on 2.12.3-2.12.6, possibly earlier. ``` error: java.lang.AssertionError: assertion...
2.12 REPL can't re-eval a compiled script that contains a class definition because it attempts to forward all definitions from the wrapper class. ``` $ scala Welcome to Scala 2.12.6...
The following should not compile; `outerd` cannot prove that there exists one `E` that unifies the `left.S` and `right.S`, but introduces one anyway. We use that to throw a `ClassCastException`....
Unfortunately no minimal right now, as this appears only when I run a whole test suite - on single test it works ok. Failing test is in expression evaluator PR...