About the guidelines, from https://rust-lang.github.io/api-guidelines/about.html https://rust-lang.github.io/api-guidelines/about.html > This is a set of recom

About the guidelines, from https://rust-lang.github.io/api-guidelines/about.html https://rust-lang.github.io/api-guidelines/about.html > This is a set of recommendations on how to design and present APIs for the Rust programming language. They are authored largely by the Rust library team, based on experiences building the Rust standard library and other crates in the Rust ecosystem. GitHub repo for the guidelines: https://github.com/rust-lang/api-guidelines https://github.com/rust-lang/api-guidelines I am submitting the OP link to HN because I believe that these guidelines are useful to many people that have, or wish to, publish Rust crates that other people will then use. Following these guidelines will make the crates we make feel "native to Rust" for other people that want to make use of our crates. I found these guidelines just a couple of days ago for the first time, in spite of having written Rust for several years now. And I suspect that many others may not have read these guidelines and that others will benefit from reading them too.