Add decompress_with_limit to handle ring buffers

[peckpeck]

Decompress does not limit how many bytes it writes to the buffer.

This means that we will lose any byte present before the call, which is not a problem when we decompress all in one go, but is annoying when we want to use the buffer as a ring buffer.

So I added a decompress_with_limit which takes a maximum number of bytes to decompress. With it, it is possible to use the output buffer as a ring buffer, just don't overwrite bytes that have not yet been consumed.

[oyvindln]

This looks fine though I'm not entirely clear on what this achieves that over just limiting the length of the output slice you are passing in achieves?

[peckpeck]

It is mostly the same as limiting the length of the output slice, except that it is not possible to change this length in practice when you are not passing TINFL_FLAG_USING_NON_WRAPPING_OUTPUT_BUF since the output slice is required to contain old data and have a size of the power of 2.

[peckpeck]

I added a little more documentation to explain that usage

[peckpeck]

You do not seem to be convinced

[oyvindln]

Nah it looks fine, I've had some extra health issues recently so haven't had the energy to look over things and there aren't any other maintainers on this library. Will try to check over this and the issue you posted sometime within next week.

I don't really have any objections to it, though I do want to make sure changing what is checked against in the buffer doesn't have any impact on performance characteristics.

[peckpeck]

I'm sorry to hear that. I hope you go well.
Thank you for your time.