summaryrefslogtreecommitdiff
path: root/bincompat-forward.whitelist.conf
diff options
context:
space:
mode:
authorAdriaan Moors <adriaan.moors@typesafe.com>2013-02-08 15:05:03 -0800
committerAdriaan Moors <adriaan.moors@typesafe.com>2013-02-09 18:10:15 -0800
commitf9550c6ab8b72221ff68bbadcbcc423ebd37f4d5 (patch)
tree47fbb515c45922179d6cd4784b1431892bed72bd /bincompat-forward.whitelist.conf
parentaf0da51e1bf81c4ea1a28af227179141604f9dfe (diff)
downloadscala-f9550c6ab8b72221ff68bbadcbcc423ebd37f4d5.tar.gz
scala-f9550c6ab8b72221ff68bbadcbcc423ebd37f4d5.tar.bz2
scala-f9550c6ab8b72221ff68bbadcbcc423ebd37f4d5.zip
[nomaster] Revert "Fixes SI-6521, overrides Range#head to be faster"
This reverts commit a557a973608a75c7a02f251bbcf49fe6f6b6655e. This is necessary to maintain binary compatibility with 2.10.0. Mima says: matchName="scala.collection.immutable.Range.head" problemName=IncompatibleResultTypeProblem The bridge method appeared because result is now Int, whereas the super-method's result type erases to Object
Diffstat (limited to 'bincompat-forward.whitelist.conf')
-rw-r--r--bincompat-forward.whitelist.conf8
1 files changed, 4 insertions, 4 deletions
diff --git a/bincompat-forward.whitelist.conf b/bincompat-forward.whitelist.conf
index 28c8a33fa2..1ff6cc6012 100644
--- a/bincompat-forward.whitelist.conf
+++ b/bincompat-forward.whitelist.conf
@@ -21,10 +21,10 @@ filter {
problemName=MissingMethodProblem
},
# TODO: revert a557a97360: bridge method appeared because result is now Int but the super-method's result type erases to Object
- {
- matchName="scala.collection.immutable.Range.head"
- problemName=IncompatibleResultTypeProblem
- },
+ # {
+ # matchName="scala.collection.immutable.Range.head"
+ # problemName=IncompatibleResultTypeProblem
+ # },
# TODO: revert 0b92073a38 2aa66bec86: SI-4664 [Make scala.util.Random Serializable] Add test case
{
matchName="scala.util.Random"