Document soundness status

[autumnontape]

I know it's been a while since there was a commit to this project, but I also know people are still on your case about this, and my hope is that full transparency will get them off of it. I'm also keeping in mind that you asked for a pull request in #30.

You'll need to publish a new version to crates.io, even if there have been no code changes, in order to make the textual changes since the last published version visible there and on docs.rs.

[CLAassistant]

All committers have signed the CLA.

[nox]

Full transparency would be making all methods that return a Completion unsafe. I already asked the author of this crate if they would approve a PR doing that but I've yet to get an answer back.

[autumnontape]

@nox I agree that fixing the API would be ideal, but I also suspect that there will always be a set of crates that don't use unsafe as intended for one reason or another, and what's most important is being able to tell the difference right away.

[autumnontape]

@spacejam Is rio abandoned?

[spacejam]

@autumnontape thanks for this PR! LGTM. rio is not abandoned, but I work on it as I have motivation to do so, and all of the negativity that people have dumped on me has basically dropped that motivation to 0 for the time being. As sled needs better io_uring support I'll support the features I benefit from, and if friendly folks care to push the codebase forward in ways that they will personally benefit from I'm more than happy to mentor them and work together, and that would probably also spark my motivation in general, because I get a lot of enjoyment out of sharing knowledge. So, for the time being, it's in a state of "waiting for motivation to come back" which probably won't happen until new people I haven't blocked yet stop making attacks on me in various places on the internet over this. In general I want to spend my energy on communities that engage respectfully with me and help to push things forward. Do a search on twitter for this crate's url and you'll see some really gross stuff. It's led to me feeling like the async subcommunity of rust is the most toxic group of humans I've ever had the misfortune of interacting with over technical matters, and it's made me spend more time on my database and distributed systems projects that let me engage with people who seem to be a nice intersection of {friendly, knowledgeable, measure what they use instead of rabidly spewing garbage}.

[spacejam]

published