In Diesel, there was a trait that exported a method
.into(). When this trait was not in scope, it would think that the
Into::into of stdlib was being called and complain about the wrong number of parameters, which was confusing.
The name has changed since then, but taking also account the possibility that an overlapping method of a trait that is not in the scope may improve UX even further. (On the other hand, it might clutter up the error message.)
I’m thinking of something like:
Or, did you mean to call this another method of trait T? In that case, the trait must be in the scope:use T``.