Open hasufell opened 1 week ago
I wonder if there is a point of more general application; that the Stackage 'social contract' for maintainers should have something express on the broader topic (one way or the other).
I think portability guarantee is essential for industrial users. Building a binary in some CI only to have it crash in production with "illegal CPU instruction" seems like a disaster.
Sure, you can always argue "you gotta know what you are doing", but stack/stackage have always strived for predictable behavior.
Since hashable 1.4.5.0 there is a new flag that does:
This horrible hack may break anyone's release binaries who didn't catch this by accident. So stackage should force this flag off.
Also see https://github.com/haskell-unordered-containers/hashable/issues/310