-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Tue, Nov 25, 2008 at 3:21 PM, Duncan Coutts wrote:
On Sun, 2008-11-23 at 22:53 -0500, Gwern Branwen wrote:
So I was trying to compile lambdabot with cabal-install. Lambdabot uses Template Haskell for generating some boilerplate, and it was a failed dependency. Template Haskell uses packedstring for... something... and packedstring was a failed dependency: Data/PackedString.hs:83:7: Could not find module `Data.Data': it is a member of package base, which is hidden
Now this is a problem, but it's not the problem I am interested in. I am interested in: why is template-haskell using packedstring? Wasn't packedstring obsoleted years ago?
Yes.
The question is if one should break the TH api just to remove this deprecated dependency. Especially when it is slated to be replaced with an improved unicode packed string type in the future.
So either we break it once, or twice.
Duncan
I don't really see why we would need to change the API; let's just make the types = String, and the conversion functions null-ops. Unless there's some sort of low-level binary API compatibility you are referring to? - -- gwern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAkkzAIMACgkQvpDo5Pfl1oIbkwCfb1Bx87CqVolvdWL0ZFOwclCa x5kAnjg+EAqUJuE+mR0KLclMS1fQPn67 =d5hQ -----END PGP SIGNATURE-----