Scala Buggabot

@retronym said: Upcasting the scrutinees of the patterns disables pattern matcher analysis, which is the part that blows the stack and/or takes ages to compute: ``` diff --git a/src/main/scala/intswitch/PlainBenchmark1024.scala b/src/main/scala/intswitch/PlainBenchmark1024.scala...

@retronym said: Minimized: https://gist.github.com/f865bae6271477425eda2b436352ddb8 `test.scala` compiles in 12s (although takes significant heap in the backend to eliminate dead code) `test2.scala` blows the default stack in: ``` at scala.tools.nsc.transform.patmat.Solving$Solver.findTseitinModelFor$(Solving.scala:471) at scala.tools.nsc.transform.patmat.PatternMatching$OptimizingMatchTranslator.findTseitinModelFor(PatternMatching.scala:89)...

@retronym said (edited on Dec 5, 2016 10:21:47 PM UTC): Might be a duplicate of #10057, although this one seems to manifest in a compilation without exhaustiveness warnings, which is...

@retronym said: I was trying a few things to optimize `findTseitinModelFor` (patch; https://gist.github.com/6ba30b3bbfd76715cfd1821f77c6075a), but we need to look at this in the broader context of the unreachable analysis, which appears...

Imported From: https://issues.scala-lang.org/browse/SI-7108?orig=1 Reporter: Eastsun (eastsun) Affected Versions: 2.11.0-M1

@paulp said: How can this possibly be right: ```scala pt1 match { // if at least one of the types in an intersection is checkable, use the checkable ones //...