* Jeremy Shaw: > The place where you really run into trouble is when you depend on two > libraries which both contain an orphan instance for the same type. > There is nothing you can do to work around that, AFAIK. And, that is > part of what makes orphan instances risky. On the other hand, that has > never happened to me in 10 years of Haskell programming. So, that is > probably why there isn't much clamoring to do something about it.
It's also not different from a scenario where two libraries use two types for exactly the same concept (IPv4 addresses) or closely related ones (strings as bytes, UTF-8, UTF-32 etc., or different kind of number types in SML). In the end, lack of global coordination will always require some ugly plumbing, no matter how fancy the language is. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
