self isn't always the first argument, though It's not for foo<T: Trait<U>, U>(x: bool, y: T, z: U), and you'll have similar problems here the UFCS call is basically eq<T: PartialEq<U>, U>(&T, &U)
-
of course, my example is kinda contrived, but trait constraints can bubble out of inference in weird action-at-a-distance ways at times as well.
Sure. I feel like the biggest supporting argument for all of this is that if in any ambiguous case for these the impls it could pick behave remotely differently, your code is already crazy ambiguous
-
-
yeah definitely, mostly trying to underscore the point that this problem is larger than just functions, and while we might get the most utility out of adding a special case step for functions, it's important to look at it as a more general thing
-
Yes. I appreciate the concrete example demonstrating where this applies outside of function calls. I mistakenly thought that was the only place. It's really any place there can be multiple type generic types interacting
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.