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
Error:(11, 4) type mismatch;
found : sre.task.Core.WithVariables[Item[A]]
required: sre.task.Core.WithVariables[Item[Element]]
Note: implicit value elementIteratorForIterator is not applicable here because it comes after the application point and it lacks an explicit result type
@typeclass trait ElementIterator[It[_]] {
I am not sure what happens here. It seems to me when Element is used in the implicit parameter list it will be freshly assigned to a new type variable A instead of matching it with the one in iterators type.
What I really want is to have is a WithVariables with the same type parameter as It.
What is really happening here? Is this a bug?
I originally asked for help on SO and a @Jasper-M suggested me as a workaround to add the @noop annotation to the method, which works.
I don't know if it should go in a separate issue, but I have another method originally in the type class with what seems to be an eligible type for generating an Op, however it is not done. So having this method:
I have a hard time defining the following typeclass:
I get the following error:
I am not sure what happens here. It seems to me when
Element
is used in the implicit parameter list it will be freshly assigned to a new type variableA
instead of matching it with the one initerator
s type.What I really want is to have is a
WithVariables
with the same type parameter asIt
.What is really happening here? Is this a bug?
I originally asked for help on SO and a @Jasper-M suggested me as a workaround to add the
@noop
annotation to the method, which works.I don't know if it should go in a separate issue, but I have another method originally in the type class with what seems to be an eligible type for generating an Op, however it is not done. So having this method:
This compiles:
However this not:
The text was updated successfully, but these errors were encountered: