Data.Validity.ByteString

A ByteString is NOT trivially valid.

The offset and the length both need to be positive. Note that the length does not need to be greater than, or equal to, the offset.

TODO there's nothing we can do about the foreign pointer, I think?

A lazy ByteString is valid according to its chunks.

Trivially valid

My guess is that short bytestrings are not trivially valid but there is no way to access the internals.