Thread

For those (like me) who don't want to sit through a long video here's the PDF: https://web.eecs.umich.edu/~imarkov/10rules.pdf nostr:nprofile1qyvhwumn8ghj7mrfva58gmnfdenhyetvv9ujucm0d5hszrnhwden5te0dehhxtnvdakz7qpq4nyjtt7u09jtyvy3tdy06zmct2evsk552q4ye69303acpkulkzas8dpgn3 to answer your question, simple coding rules like this do sound like a good idea. Ideally the rules should be enforceable via clippy and checked automatically in CI. For BDK's CI we already check default clippy and fmt rules, unit test coverage, rustsec audit, and building with different features combinations including no-std and using our MSRV. If anyone knows of a version of these rules adapted for Rust let me know, I'd love to take a look. For a broader description of Rust best practices I like this book: https://www.lurklurk.org/effective-rust/