aboutsummaryrefslogtreecommitdiff
path: root/tests/pos/overloaded.scala
Commit message (Collapse)AuthorAgeFilesLines
* Refine pretypeArgsMartin Odersky2016-03-091-1/+23
| | | | | It worked more or less by accident before. Now it's more complicated, but we also have tests.
* Pretype functional arguments when doing overload resolutionMartin Odersky2016-03-091-0/+4
|
* Reverting decision what constitutes a double def.Martin Odersky2014-03-211-7/+7
| | | | | | | | | | | | | | | test case t0273. Was positive in Scala 2, is now deemed to be negative. Two two definitions def a = () => () def a[T] = (p:A) => () do have matching signatures, so should constitute a double definition. I previously thought that we can get away if the two definitions have different result types, but then you immediately have a problem because the denotations have matching signatures for the pruposes of "&" yet cannot be merged. Which of the two definitions would override a definition in a base class is then an arbitrary decision.
* Fix to overloading resolution: prioritize non-methods over methods.Martin Odersky2014-01-061-1/+3
| | | | If one alternative is a non-method yet the other is a method (of type PolyType or MethodType), the first alternative is "as specific as" the second.
* Making sure New's always end in an application.Martin Odersky2013-12-181-0/+12
|
* Special handling of implicit members.Martin Odersky2013-12-171-0/+10
The previous treatment would force all members, causing cyclic reference errors. We fix it by filtering early in computeMemberNames itself for implicits.