summaryrefslogtreecommitdiff
path: root/test/files/neg/t5452.scala
Commit message (Collapse)AuthorAgeFilesLines
* Closes #5452.Hubert Plociniczak2012-02-171-0/+29
| | | | | | | | Instead of trying to track the fallback attempts we rely on the context state to inform us which fallback is the last one. setError cannot always be called in NoBestMethodAlternativeError because inferMethodAlternative relies on side-effects. Review by @paulp.
* Revert "Fix for SI-5452."Paul Phillips2012-02-151-29/+0
| | | | This reverts commit 2b731911e97a281e324060099631e2374b2144ec.
* Fix for SI-5452.Paul Phillips2012-02-131-0/+29
Why is calling the error function not enough to register the error, why does "setError(tree)" have to be called as well? That was the cause of this particular stackoverflow. In ContextErrors I see lots of methods which call setError and lots more which do not, and frankly it's all pretty terrifying. There is zero documentation attached to setError. Maybe there's an explanation somewhere I'm not seeing. Review by @hubertp.