Jonathan Immanuel Brachthäuser
Jonathan Immanuel Brachthäuser
Agreed, there should be tests. I simply forgot to add the file :(
The corresponding (ambiguity) error message has been fixed in lampepfl/dotty#9834, but this did not change the overloading behavior.
I think there are two aspects to this issue: - overloading context functions in general - inference of type arguments `A` and `B` in your example If we monomorphize the...
I think I understand your usecase. But I am not sure how one could implement such a catch all implicit without giving up clarity in other use cases. In particular,...
Hence my strong intuition that we want to avoid overloads that only vary in the arguments of context functions. What do you think @smarter ?
@neko-kai Sorry, you are completely right. I shouldn't have used "covariant", more "return position". It is a bit difficult to explain for me, but arguments to contextual function-parameters feel much...
@prolativ Regarding the DSL example: I completely agree that this would be a clear way to express it. For my example above: I still think both would make sense and...
While @neko-kai's use case is important, I am closing this issue since it is not a bug with respect to the current specification of context functions.
Reopening as a feature request
Hey thanks for looking into it. Maybe I reduced it too much :( In the original compiler adding the type annotation to `unification` does not help and I still get...