-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Sun, Nov 30, 2008 at 5:56 PM, Duncan Coutts wrote: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAkkzI7cACgkQvpDo5Pfl1oKiKQCghkRpR7vRjyTezciI9Hv/HUFX FygAmwdCS57mUfqUc2N8Dm5ceFNC2CNn =ABN1 -----END PGP SIGNATURE----- ...
Ah, I see. I'd not looked that closely. It's this bit you're referring to:
type OccName = PackedString mkOccName :: String -> OccName occString :: OccName -> String
type ModName = PackedString mkModName :: String -> ModName modString :: ModName -> String
type PkgName = PackedString mkPkgName :: String -> PkgName pkgString :: PkgName -> String
Technically that's not an abstract api so changing the type alias could break programs, though I agree that it may be unlikely.
I would argue that it's less unlikely than richly deserved. :) (I find it difficult to imagine why a TH hacker would deliberately tunnel through the alias, personally.)
Unless there's some sort of low-level binary API compatibility you are referring to?
No, just the source level API.
Duncan
OK. Is the previous issue a fatal objection or can we just make the change and upload a new TH? -- gwern