| ... | ... | @@ -21,7 +21,7 @@ Two forms of binary I/O are considered here: |
|
|
|
|
|
|
|
## Proposal 2 - The Binary class
|
|
|
|
|
|
|
|
- Proposal two is to add a Binary class, based on the type class described in [ The Bits Between The Lambdas](ftp://ftp.cs.york.ac.uk/pub/malcolm/ismm98.html). The advantage of this form of binary I/O over the simpler System.IO library is support for serialising more complex data types, using type classes to recursively define binary I/O routines for each component of the type. Instances of I/O may be written by hand, or derived mechanically with [ DrIFT](http://repetae.net/john/computer/haskell/DrIFT/). Ideally Binary would be derivable by the compiler (is this feasible?).
|
|
|
|
- Proposal two is to add a Binary class, based on the type class described in [ The Bits Between The Lambdas](ftp://ftp.cs.york.ac.uk/pub/malcolm/ismm98.html). The advantage of this form of binary I/O over the simpler System.IO library is support for serialising more complex data types, using type classes to recursively define binary I/O routines for each component of the type. Instances of I/O may be written by hand, or derived mechanically with [ DrIFT](http://repetae.net/john/computer/haskell/DrIFT/). Ideally Binary would be derivable by the compiler (as is done currently in nhc98), or perhaps using some form of datatype-generic declarations (see [DerivedInstances](derived-instances)).
|
|
|
|
|
|
|
|
## References
|
|
|
|
|
| ... | ... | |