Georgi Krastev
Georgi Krastev
We should make up our mind 😄 - the warning is wrong about varargs: ```scala Welcome to Scala 3.5.1-RC1-bin-SNAPSHOT-nonbootstrapped-git-952b928 (17.0.9, Java OpenJDK 64-Bit Server VM). Type in expressions for evaluation....
About `foo4`, I think exhaustiveness is not checked when using custom `unapply` methods :thinking:
This doesn't seem to work in Scala 2. Still doesn't warn: ```scala object A { def unapply(x: Int): Some[Int] = Some(x) } 42 match { case A(5) => 5 }...
Ah so it works if the custom `unapply` is a leaf but not when it's a branch in the pattern match. Well that's confusing :confused:
Related? #11457
Still a problem in Scala 3 😞
There are a lot of existential types in this example that make me feel uneasy (there's even a warning about them). Which naturally leads to the following definition that does...
I don't know. There are many issues about existential types. It's probably not so much the implicit search being involved, but rather type inference messing up with skolems and type...
Actually in this example implicit search does matter, because internally it uses an existential abstraction to find implicit candidates.
It should be possible to support for any size tuple in a generic way