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
I would expect this code to compile as it does on Scala 2. assertLazy is completely polymorphic in its type other than being by name, which fromEither satisfies, so this should work. The issue appears to be related to the fact that the argument to fromEither has two type parameters. If I try it with an argument with only one parameter it works correctly.
The text was updated successfully, but these errors were encountered:
When we reach out to get the callee type, we might get an error, e.g.
if the callee is overloaded. Example:
```
ch => sb.append(ch)
```
Here we might want to call calleeType to find the argument type
of `sb.append` in order to use this type as the type of `ch`. But
this fails since `append` is overloaded on StringBuffer.
Prevously this did not matter since we called calleeType only as a last
effort, so if it failed the whole typing failed. But with the changes
forseen for fiing scala#8111 we need to be able to compute calleeType and
retract it if it does not work.
minimized code
expectation
I would expect this code to compile as it does on Scala 2.
assertLazy
is completely polymorphic in its type other than being by name, whichfromEither
satisfies, so this should work. The issue appears to be related to the fact that the argument tofromEither
has two type parameters. If I try it with an argument with only one parameter it works correctly.The text was updated successfully, but these errors were encountered: