Tony Arcieri
Tony Arcieri
This approach wouldn’t work with README.md files
I put the usage docs where they are already because I like for the README.md to be a high-level overview and for the detailed usage docs to be in the...
I think we've received a lot of complaints about people having trouble trying to find the documentation when they have to click through to the trait crate, and then the...
I was making a general comment on the overall state of the documentation across the project. I can’t say I’ve specifically heard people complain about `aead`. One comment I’ve seen...
I'll note a big disadvantage of trying to put *all documentation* in README.md as opposed to splitting out e.g. usage details into standard rustdoc is you can't use intra-doc links,...
I strongly disagree. People get confused by not having documentation that's directly relevant and applicable to their crates, with copy-paste examples that Just Work. Trying to put all of the...
For `serpent` specifically I was thinking of adding a typed wrapper like `SerpentN` which is just a newtype for `Serpent` but generic around a phantom key size (and maybe a...
Sure, sounds good
There was a self-audit as part of the test suite but it was removed at some point. In lieu of that we can probably try to dogfood `rustsec/audit-check`
Note: I only ran `cargo fix` on the 64-bit soft backend. There's so much conditional compilation it might be a bit difficult to track down all the places this lint...