TRex is already mentioned on the wiki as coming at a too high implementation cost.
2011/9/15 J. Garrett Morris <jgmor...@cs.pdx.edu>: > On Thu, Sep 15, 2011 at 6:03 AM, Barney Hilken <b.hil...@ntlworld.com> wrote: >> The right way to deal with records is first to agree a mechanism for >> writing a context which means >> >> "a is a datatype with a field named n of type b" >> >> then give the selector n the type >> >> "a is a datatype with a field named n of type b" => n :: a -> b >> >> There is no reason why this shouldn't be used with the current syntax >> (although it might clash with more advanced features like first-class >> labels). > > Trex is one existing approach in the Haskell design space > http://web.cecs.pdx.edu/~mpj/pubs/polyrec.html > http://web.cecs.pdx.edu/~mpj/pubs/lightrec.html > > /g > > -- > "I’m surprised you haven’t got a little purple space dog, just to ram > home what an intergalactic wag you are." > > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://www.haskell.org/mailman/listinfo/glasgow-haskell-users > _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
