Closed liamzee closed 1 year ago
It looks like aeson is binned to bytestring 11.x, whereas many packages are moving onto bytestring 12. Is there a plan for compatibility with bytestring 12, or is aeson planning to stick at bytestring 11 for a while?
aeson will add bvtestring-0.12 support when it is bundled with a released GHC.
bvtestring-0.12
@liamzee: Issue should be fixed now, according to https://github.com/haskell/aeson/pull/1055#issuecomment-1747587968.
It looks like aeson is binned to bytestring 11.x, whereas many packages are moving onto bytestring 12. Is there a plan for compatibility with bytestring 12, or is aeson planning to stick at bytestring 11 for a while?