úÎ!Ö4NoneÑvalidity-bytestringTrivially validgMy guess is that short bytestrings are not trivially valid but there is no way to access the internals.validity-bytestringA lazy  ByteString" is valid according to its chunks.validity-bytestringA  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.BTODO there's nothing we can do about the foreign pointer, I think?Safe       2validity-bytestring-0.4.1.0-4XiaUPy4TuB8HYXWDs3z5OData.Validity.ByteStringPaths_validity_bytestring$fValidityShortByteString$fValidityByteString$fValidityByteString0version getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName