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
Output from scalac 2.10.3 is attached (tried to post it here in the description, but JIRA mangled it).
Exception in thread "main" java.lang.IllegalArgumentException: Could not find proxy for val x2: Tuple2 in List(value x2, method apply, <$anon: Function1>, value <local A>, object A, package <empty>, package <root>) (currentOwner= value x )
The text was updated successfully, but these errors were encountered:
Chris Martin (chris-martin) said:
Sorry I can't be more specific with my description than "compiler error", but I don't understand the problem well enough to elaborate any further.
This smells rather similar to #8111, but it isn't the same bug.
qbin/scalac -Ycheck:typer ../scala/sandbox/test.scala
[Now checking: typer]
[check: typer] ../scala/sandbox/test.scala:8:
currentOwner chain: value $anonfun -> value <local A> -> object A
symbol chain: value x -> value $anonfun -> value <local A> -> object A -> package <empty> -> package <root>scala.reflect.internal.Trees$Bind / (x @ _)
[check: typer] ../scala/sandbox/test.scala:8:
currentOwner chain: value $anonfun -> value <local A> -> object A
symbol chain: value y -> value $anonfun -> value <local A> -> object A -> package <empty> -> package <root>scala.reflect.internal.Trees$Bind / (y @ _)
warning: TreeCheckers detected non-compliant trees in test.scala
@som-snytt said:
I did check it against the #8111 patch last night, but only got as far as noticing that changing the operator name from - works around it.
@retronym said:
As @xeno-by said, the symbols appear to be open revolt this year.
As you've probably gleaned now, the name of the operator is only relevant in that it must be one that exists on the original function, before the implicit view is tried.
Output from scalac 2.10.3 is attached (tried to post it here in the description, but JIRA mangled it).
The text was updated successfully, but these errors were encountered: