0.1.3 violates PVP

[phadej]

The flags introduced in that release are automatic, therefore solver can turn them off on will. And it very much does with later GHCs, as text bound is <1.3.

So one cannot rely that Text, Vector and ByteString instances exist.

These flags should have been manual, and 0.1.3 release kind of violates PVP as it allows removal of the instances. Reverse dependency packages have no way to ensure the instances exist.

[erikd]

@phadej What do you suggest we do? A new 0.2.0 release and deprecate 0.1.3 ?

[phadej]

@erikd yes.

[michaelpj]

Here's an example where this came up recently. vector-0.13 was released. This led to us losing the vector instances, because cabal prefers to pick vector-0.13 and turn off the vector flag in nothunks. Whereas I want the constraint to go the other way: I need the vector instances, so I want cabal to be forced to pick vector < 0.13.

[phadej]

Err. Sorry. There is no need for 0.2.0. I would

• make a revision with base <0 for 0.1.3 to pretend it never existed (bad release).
• make a 0.1.4 release with manual flags enabled by default, if the toggling functionality is really needed.

cc @Bodigrim who introduced the change.

[michaelpj]

This is still a problem.

[Bodigrim]

As a Hackage trustee I made a revision allowing text-2.0 and vector-0.13, which should suffice for now.
https://hackage.haskell.org/package/nothunks-0.1.3/revisions/

[michaelpj]

Just to be clear, I think the issue will recur if vector-0.14 is released.

[phadej]

Or text-2.1 (as there is already merged breaking change in texts master).

[phadej]

As a Hackage trustee I'll make a blacklisting base <0 revision in few weeks. It have been six months to fix the issue.

(EDIT: and the fix is trivial #17 (comment), make flags manual and enabled by default and reupload new version)

[coot]

nothunks-0.1.4.0 is on hackage.

[coot]

I also published a new revision of nothunks-0.1.3 with base <0.