You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@gaydenko said:
From my ordinary Scala user's POV additional degree of freedom just complicate the code. For named arguments "all or nothing" rule seem more acceptable, IMHO.
@OlegYch said (edited on Dec 3, 2011 6:40:34 PM UTC):
looks like the issue requires a bit more attention
it still doesn't compile in case of several overloads and error message is really misleading:
classc {deff(a:Int, b:Int) =1; deff() =1}
new c().f(a=1,2)
fails with
<console>:18:error: overloaded method value f withalternatives:
()Int <and>
(a: Int,b: Int)Int
cannot be applied to (a: Int, Int)
new c().f(a=1,2)
tested with 2.8.0, 2.9.1 and scala-2.10.0.r25912-b20111031024940
The following code ought to compile.
The text was updated successfully, but these errors were encountered: