>
> This is conceptually equivalent to the haskell rule that a type class
> instance must either be provided in the unit of compilation that introduces
> the type class or in the unit of compilation that introduces the type.
>
Right, but in Haskell, it's a warning; in Rust it's an error.
That allows a check for non-overlapping instances, but it doesn't address
> the problem of instance resolution, e.g. for List<'a> vs List<char>.
>
Agreed.
--
Alex R
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev