Switch Data.Text.Array to Data.Array.Byte#474
Conversation
|
This is technically a breaking change as An example of possible problems: any instances for |
|
I hoped no one ever defined instances for |
You cannot ever know what (kind of weird stuff) people do in private projects. IMO we cannot assume no-one does anything weird, only that is very rare. EDIT: PVP is also quite unambiguous, breaking change is breaking change even no-one observes it. Someone might observe it in future by writing instances to ease transition! (though they probably end up needing to use CPP, having CPP-guards at major bounds is definitely more welcome). |
|
Perhaps this has to wait until GHC 9.4 becomes a bootstrap version, otherwise I imagine Hadrian might be troubled... |
8dbb6dd to
021211b
Compare
|
Cf. haskell/primitive#359 and haskell/bytestring#410. This is now pending FreeBSD build investigation in #475. |
82b2b81 to
65ac808
Compare
|
Once GHC 9.6 is released, GHC 9.4 will become the oldest bootstrap compiler. So we are free to merge this right after we cut a release for GHC 9.6, which is fairly soon I hope. |
|
What's the issue with GHC before 9.4? Hadrian is allowed to depend on things on Hackage. |
|
This is ready for review now. Both haskell/primitive#359 and haskell/bytestring#410 have been merged. |
|
Another breaking change that this PR brings about (aside from the discussion about instances in #474 (comment)) is that you will no longer be able to import import Data.Text.Array (Array (..))The |
This is a part of a grand plan to unify
ShortByteString,Data.Text.ArrayandData.Primitive.ByteArrayto share the same data type. If it looks good, I'll make a release ofdata-array-bytepackage.