An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules
Need to keep a lot of things in mind to make sure your crate has great interoperability with the existing Rust ecosystem, e.g. because of the orphan rule the users of your crate won't be able to implement the traits defined in std or serde for the types from your crate, so you have to decide which ones it makes sense to implement and provide that implementation yourself.
The Rust package manager
It is currently not possible to specify that a certain version of a crate implementing some cargo-* subcommand must be installed when working on my crate. It's quite limiting, especially coming from JS where you can explicitly declare a cli package as a dependency of your own package and use it in build scripts, etc.
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.
Cargo subcommand `release`: everything about releasing a rust crate.
Use cargo-release and setup pre-release hooks and replacements.
cargo-update - A cargo subcommand for checking and applying updates to installed executables
2 projects | reddit.com/r/rust | 22 Feb 2022
Code-signing rust binaries for Apple Silicon?
2 projects | reddit.com/r/rust | 31 Dec 2021
Is it possible to specify cargo plugins required for development with a project?
2 projects | reddit.com/r/learnrust | 17 May 2022
cargo-edit v0.9 released!
6 projects | reddit.com/r/rust | 28 Mar 2022
Cargo: Namespaced and weak dependency features have been stabilized
4 projects | reddit.com/r/rust | 2 Feb 2022