Our great sponsors
-
rust-orphan-rules
An unofficial, experimental place for documenting and gathering feedback on the design problems around Rust's orphan rules
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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.
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.
Use cargo-release and setup pre-release hooks and replacements.