summaryrefslogtreecommitdiff
path: root/test/support/annotations
diff options
context:
space:
mode:
authorJason Zaugg <jzaugg@gmail.com>2014-02-13 21:49:18 +0100
committerJason Zaugg <jzaugg@gmail.com>2014-02-13 21:58:13 +0100
commit922d090f5c2dd8a14f2bb7915a04c5156d29ea1b (patch)
tree82accbfbf13c9c492d0a43bb47c562d77c30275b /test/support/annotations
parentc83e01d47d941265fa5415c0f29a884c904fdfa0 (diff)
downloadscala-922d090f5c2dd8a14f2bb7915a04c5156d29ea1b.tar.gz
scala-922d090f5c2dd8a14f2bb7915a04c5156d29ea1b.tar.bz2
scala-922d090f5c2dd8a14f2bb7915a04c5156d29ea1b.zip
SI-8276 Test for cyclic error caused by (reverted) SI-1786 fix
We reverted SI-1786 recently on the grounds that its means of avoiding cycles (not sharpening bounds of T[_] when T is uninitialized) caused unacceptable non-determinism (well: compilation order dependency) to type inference. Nary a day later, @gkossakowski hit a regression in scala-io. Bisection revealed that it stopped working in 2dbd17a2 and started working agiain after the revert. How's that for prescience! I've distilled the cyclic error in scala-io in this test case. I'm yet to pinpoint this, followon error, which didn't survive the shrink ray, and only appeared in the original code: error: java.lang.IndexOutOfBoundsException: 0 at scala.collection.LinearSeqOptimized$class.apply(LinearSeqOptimized.scala:51) at scala.collection.immutable.List.apply(List.scala:83) at scala.reflect.internal.tpe.TypeMaps$AsSeenFromMap.correspondingTypeArgument(TypeMaps.scala:5
Diffstat (limited to 'test/support/annotations')
0 files changed, 0 insertions, 0 deletions