On Sun, Jul 6, 2014 at 2:30 PM, Matt Oliveri <[email protected]> wrote:
> Come to think of it, how does an interface differ from a full blown > object then? Interfaces consist exclusively of methods. No data fields. > And correspondingly, how does the "Castable" type class > differ from a "Coercion" type class for implicitly coercing between > arbitrary types? > Two names for the same thing. I may have made a mistake and swapped names somewhere along the way. The "Castable" or "Coercion" type class says what X's and Y's may appear in "x:X as Y". The associated type class instance says what that expression actually means. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
