Moritz Borcherding

I noticed that eventfd is actually not unix but linux specific. I provided an implementation using regular pipes that should work on all and hide eventfd behind a feature flag....

> I noticed that eventfd is actually not unix but linux specific. I provided an implementation using regular pipes that should work on all and hide eventfd behind a feature...

It seems like freebsd has something similar ([source](https://lwn.net/Articles/801319/)) but other BSDs dont. Also it's linux 5.4+. I'd like to avoid having too many optional mechanisms so I'm probably not going...

I hate that capitalized letters in a github name cause this much trouble when using go, I had this issue a while ago with my own and others packages too....

I should propably update the Readme with that disclaimer tbh :D > I do not recommend to use this package but to use the one of klauspost here. It has...

I theory you are right, zstd could be implemented using none of the std lib. This implementation does use `std::vec::Vec` in many places, because it is 1. convenient 2. Probably...

Right I didn't think about wasm, that is a pretty big thing. If I understand correctly, the only thing that would need to be changed would be the imports of...

Replacing the Hashmap is no problem, it's just used for the dictionary lookup once per zstd stream (and only if a dict is used). I could just make this a...

You are right using the std::io::Read makes it hard to port to no_std. But I really don't want to replace it. Maybe the errorhandling working group will succeed in pushing...

Well there is still the issue of std::io::Read/Write being used a lot throughout the codebase. These do not exist in core afaik. I am not really involved in no_std development,...