Jørgen Ibsen

Regarding streaming, if you are on Linux you could try simply specifying stdin and stdout as filenames, like: ~~~.sh ./blzpack -9 /dev/stdin /dev/stdout foo.blz ~~~

Sorry about the delay. I largely agree with your concerns about the worst-case behavior of the optimal level. But I feel it provides both an interesting data point and a...

That looks great, thanks a lot!

@jirutka, just wanted to ping you about the new release 1.2.0 in case you wanted to update your bindings. I don't know enough about Lua to make a PR myself.

From a quick look at the code, I am guessing: ``` .patch diff --git a/libzling/libzling_lz.cpp b/libzling/libzling_lz.cpp index 336adf6..3cc7f93 100644 --- a/libzling/libzling_lz.cpp +++ b/libzling/libzling_lz.cpp @@ -294,6 +294,9 @@ int inline ZlingRolzEncoder::MatchLazy(unsigned...

Thanks for the contribution, I am sure nemequ will let you know if he is interested, but I just wanted to mention that for the specific range you mention there...

I just had a quick glance at the code, and am wondering if it might be better to check if `possible` is 1 at https://github.com/nemequ/munit/blob/master/munit.c#L1617 instead? My thinking is that...

Hmm interesting, I had a recollection of this being fixed before, and looks like the empty range in #30 was it, but firstly that is in the public API, not...

> My thinking is that calling `munit_rand_at_most` with a max of 0 is a bug Looks like my thinking was wrong, the ranges appear to be inclusive, so calling it...

> µnit has some, like munit_rand_int_range. @jibsen, IIRC you did some work on those functions, would you mind if I relicensed them to public domain (CC0) and merged them into...