adding a good storable vector api on top

[cartazio]

Hey all, as part of my hacking on writing a blosc-hs lib, i'll be sorting out having a good storable vector API there. That would probably be easy to apply the same work to providing that sort of api to lz4hs.

This would also probably entail enriching the header encoding info to allow (optionally) encoding the byte size of elements (when interpretable as such). Also that would probably be a good time to add a version byte to the front of the header so that future changes have the option of providing backwards compatibility

[mwotton]

if it still works with the C lz4 decoder/encoder, should be fine. otherwise better to call it something else, or discuss with Yann Collet to get protocol changes into the C lib.

[mwotton]

@cartazio do you still care about this?

[cartazio]

depends on the context of the question, though yes at some point soon i'll be resuming messing with writing some compression codes for storable and unboxed arrays I think. (might be a month or several out though)