On Sat, 23 Jan 2010 16:57:49 -0600, Jeremy Shaw <[email protected]> wrote: > On Sat, Jan 23, 2010 at 7:57 AM, Neil Mitchell <[email protected]>wrote: > > > > No, that's definitely not correct, or even remotely scalable as we > > increase the number of abstract types in disparate packages. > > > Yes.. happstack is facing another aspect of this scalability issue as well. > We have a class, Serialize, which is used to serialize and deserialize data. > It builds on the binary library, but adds the ability to version your data > types and migrate data from older versions to newer versions. > > This has a serious scalability issue though, because it requires that each > type a user might want to serialize has a Serialize instance. > > So do we:
[..] > Any other suggestions? 4. Write a new package: * serialize-text * text-instances (which would be a place holder for more instances) I would go for trying solution 2. and otherwise solution 4. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
