diff options
author | Jason Zaugg <jzaugg@gmail.com> | 2013-12-04 17:45:10 +0100 |
---|---|---|
committer | Jason Zaugg <jzaugg@gmail.com> | 2013-12-06 14:30:56 +0100 |
commit | fdcc262070470e0968afcdf0036cc18781c52e33 (patch) | |
tree | 26c07bf7bc97dc2a3f37c9180cca50d455362508 /bincompat-forward.whitelist.conf | |
parent | 7c1d1149291e1b83c96a0f6954144b9e97c030ea (diff) | |
download | scala-fdcc262070470e0968afcdf0036cc18781c52e33.tar.gz scala-fdcc262070470e0968afcdf0036cc18781c52e33.tar.bz2 scala-fdcc262070470e0968afcdf0036cc18781c52e33.zip |
SI-8029 Avoid multi-run cyclic error with companions, package object
The bug report suggests this problem only became visible in the
IDE *after* 2.10.3, but I tested an IDE with exactly 2.10.3 and
saw the same problem.
In fact, my test case fails as far back as 2.10.0. I suspect the
problem showed up after 816cecf9a9, which checks that pairs of
companion symbols are codefined eagerly in Namers.
This commit modifies the check of `rawInfo ne NoType`
in `isCoDefinedWith` to avoid triggering adaptation of types from
the previous run. I'm not sure of the precise intent of that check.
I looked at c9861cd198 (genesis of isCoDefinedWith). Before that we
get back to 3761cb4b3a1 (the dawn of Subversion.)
Diffstat (limited to 'bincompat-forward.whitelist.conf')
-rw-r--r-- | bincompat-forward.whitelist.conf | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/bincompat-forward.whitelist.conf b/bincompat-forward.whitelist.conf index 2ece671638..3b61a02bce 100644 --- a/bincompat-forward.whitelist.conf +++ b/bincompat-forward.whitelist.conf @@ -1431,6 +1431,10 @@ filter { { matchName="scala.reflect.internal.Trees#Modifiers.isDeferredNotDefault" problemName=MissingMethodProblem + }, + { + matchName="scala.reflect.internal.Symbols#Symbol.rawInfoIsNoType" + problemName=MissingMethodProblem } ] } |