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
When an extension method is defined for a typeclass more than once but with different arguments, it fails to construct if the method argument has type arguments. If we were to remove the type arguments, the method construction works.
[error] 15|valfails=MyType() +Fuzzy[1]()
[error] |^^^^^^^^^^
[error] | value + is not a member of MyType.
[error] |An extension method was tried, but could not be fully constructed:
[error] |
[error] |+() failed with
[error] |
[error] | value +: <overloaded +> does not take parameters
[error] one error found
Expectation
No error.
The text was updated successfully, but these errors were encountered:
This issue was picked for the Issue Spree 18 of July 5th which takes place in a week from now. @griggt@gagandeepkalra will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here.
In some cases while going deeper into alternatives during overload resolution,
we may end up with a nested polytype after dropping contextual parameters.
In particular this can happen for an extension with a `using` clause, as seen
in tests/pos/i11713.scala and tests/pos/i13668.scala.
The overload applicability test fails here unless the type parameter lists
are merged.
Co-authored-by: Gagandeep Kalra <gagandeepkalra1994@gmail.com>
Co-authored-by: Mark T. Kennedy <mtk@acm.org>
Fixesscala#11713Fixesscala#13668
When an extension method is defined for a typeclass more than once but with different arguments, it fails to construct if the method argument has type arguments. If we were to remove the type arguments, the method construction works.
Compiler version
v3.1.0-RC2
Minimized code
Output
Expectation
No error.
The text was updated successfully, but these errors were encountered: