Changes between Version 4 and Version 5 of Annotations


Ignore:
Timestamp:
Oct 13, 2008 3:11:03 PM (6 years ago)
Author:
batterseapower
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Annotations

    v4 v5  
    116116 
    117117=== Serialization Issues === 
     118 
     119==== Alternative 1 (Proposed) ===== 
    118120 
    119121Another disadvantage of this new annotations scheme is that currently there is no standard Binary class in the Haskell libraries. We propose to add such a beast by adding [http://code.haskell.org/binary/ Data.Binary] as a boot library and supporting automatic instance deriving for it in GHC. The advantages of doing this rather than somehow reusing GHCs inbuilt Binary class are that: 
     
    157159We have sort of the same problem outlined above even today because bytestring is a boot library. However, since bytestring isn't exported by GHC you don't end up with this sort of weird situation. (Though it might give Cabal as much of a headache as the binary problem outlined above). 
    158160 
     161 
     162==== Alternative 2 ==== 
     163 
    159164The main alternative to using binary as a boot package is to import the whole source tree for binary and bytestring but rename them to ghc-binary and ghc-bytestring respectively. This ensures there are no conflicts with user code, but: 
    160165 
     
    169174 * Etc etc... 
    170175 
     176==== Alternative 3 ==== 
     177 
    171178The other alternative we came up with is to change the GHC API to annotations to this: 
    172  
    173179 
    174180{{{