Re: Adding Binary as a constraint to the Initializable class?

> specifically the module: > http://hackage.haskell.org/packages/archive/happstack-data/0.3.3/doc/html/Happstack-Data-Serialize.html I am still unsure that types can be recovered using this library. (In other words you need to know in advance what type to expect). Cheers, JP. --~--~-~--

Re: Adding Binary as a constraint to the Initializable class?

o use a GADT to encode type info, then you > may recover type in a pre-determined universe. I don't see the details > yet though. Ah I see the comment in Yi/Dynamic now: -- Unfortunately, this is not serializable: there is no way to recover a type from a TypeRep. data Dynamic = forall a. I

Re: Adding Binary as a constraint to the Initializable class?

im's ":set [variable]=[value]" command) I know the user would expect > their changes to be restored on reload. > > Does anybody have a compelling reason I shouldnot add Binary as a > constraint to the Initializable class and update all instances > accordingly? I tried this

Adding Binary as a constraint to the Initializable class?

r changes to be restored on reload. Does anybody have a compelling reason I shouldnot add Binary as a constraint to the Initializable class and update all instances accordingly? Cheers, -Corey O'Connor --~--~-~--~~~---~--~~ Yi development mailing list yi-de

Re: Initializable

On Thu, Feb 26, 2009 at 4:52 AM, Gwern Branwen wrote: > On Wed, Feb 25, 2009 at 4:51 PM, Jean-Philippe Bernardy > wrote: >> >> Initializable is less restrictive than monoid (no mappend); so it's >> useful to keep as such. >> Adding Monoid => Initia

Re: Initializable

On Wed, Feb 25, 2009 at 4:51 PM, Jean-Philippe Bernardy wrote: Initializable is less restrictive than monoid (no mappend); so it's useful to keep as such. Adding Monoid => Initializable is ok but requires overlapping instances in many places I'm afraid. Cheers, JP. Is that ba

Re: Initializable

Initializable is less restrictive than monoid (no mappend); so it's useful to keep as such. Adding Monoid => Initializable is ok but requires overlapping instances in many places I'm afraid. Cheers, JP. On Wed, Feb 25, 2009 at 10:44 PM, wrote: > So I was wondering when I wa

patch applied (yi): Yi.IReader: generalize Seq instance of Initializable

Wed Feb 25 11:59:41 EST 2009 gwe...@gmail.com * Yi.IReader: generalize Seq instance of Initializable Ignore-this: 988b91ee989fed9dd268c901140642e5 M ./Yi/IReader.hs -1 +2 --~--~-~--~~~---~--~~ Yi development mailing list yi-devel@googlegroups.com http

Initializable

So I was wondering when I was looking at the Initializable typeclass. Would it make sense if the default Initializable for a given type could be 'mempty', if Monoid is already defined? As far as I can tell, Initializable is the same thing as Monoid except without any mappend or mco