Re: Data.ByteString.Lazy.ByteString vs Data.ByteString.Lazy.Internal.ByteString
Am 14.03.2011 06:26, schrieb C K Kashyap:
Looks like a job for Data.Binary.
> I'd like to use it with just the libraries that are part of the platform
I forgot to mention, Data.Binary does not seem to be in the platform.
Right, it is not in the platform, but I would recommend to install those packages that you find useful (and vote for packages to be included into later versions of the platform.) Interestingly, there is a hidden package ghc-binary-0.5.0.2, which almost looks like binary-0.5.0.2. Maybe ghc developers and platform maintainers could comment on any differences. If there are none you could simple "ghc-pkg expose ghc-binary". For future versions of ghc and the platform a single ghc-binary or binary version would be better. Cheers Christian
On 14/03/2011 10:33, Christian Maeder wrote:
Am 14.03.2011 06:26, schrieb C K Kashyap:
Looks like a job for Data.Binary.
> I'd like to use it with just the libraries that are part of the platform
I forgot to mention, Data.Binary does not seem to be in the platform.
Right, it is not in the platform, but I would recommend to install those packages that you find useful (and vote for packages to be included into later versions of the platform.)
Interestingly, there is a hidden package ghc-binary-0.5.0.2, which almost looks like binary-0.5.0.2.
Maybe ghc developers and platform maintainers could comment on any differences. If there are none you could simple "ghc-pkg expose ghc-binary". For future versions of ghc and the platform a single ghc-binary or binary version would be better.
You shouldn't use ghc-binary. It is indeed the same as binary, and is required because GHC uses it internally, but binary is not a platform package so we renamed it to ghc-binary and set it to be "hidden" by default. Cheers, Simon
participants (2)
-
Christian Maeder -
Simon Marlow