On Thu, Feb 10, 2011 at 1:00 AM, Ben Kloosterman <[email protected]> wrote:
> ...there is no reason you can’t have type classes for the experienced > and a simplified syntax for the new that looks and mostly behaves like what > they are used to its quite amazing how much a single element type class > behaves like an interface.... > An interface is merely a type class declaration, typically (but not inherently) one with one variable. The only thing interesting about the interface approach is that the "implements" clause gives an obviously preferred instance. What you don't typically get in an interface-oriented approach is the ability to do post-hoc interface membership, which is the place where all of the resolution confusion of type class instances is biting us. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
