On Sun, May 20, 2012 at 10:44 PM, Favonia <favo...@gmail.com> wrote: To me, typeclass seems more Haskell-ish and I would like to stick to > that if possible.
Typeclasses are perhaps the clunkiest part of Haskell. Certainly you can't say that records are less Haskellish :) > Two technical downsides of Prototype are that we > need to define all kinds of accessors, and that I am afraid it will be > slightly less efficient. I would like to understand if there are > reasons that we need Prototype. To clarify: I am fine with Prototype > as long as there's a usage for which typeclasses and records are > simply too awkward. It's very likely that I, as a beginner, overlooked > some important code in Yi. :-) > What we want to achieve is to give a number of default cases in the codebase and let the user chose one of them and extend/refine it. Perhaps you can show both encodings side by side (including client code) so we can see the pros and cons clearly. Cheers, JP. -- Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel
