Our great sponsors
-
A workspace may consists of a primary package and supporting packages. The most common case, where you need this, is when you want to use procedual macros (as they must have there own library crate). Here the main package lives in the root folder of the project and the supporting packages get subfolders in the root folder. An example for this structure is shown here: https://github.com/PyO3/pyo3 .
-
A workspace may also consists of multiple equally important packages. Here the workspace root contains an extra Cargo.toml file only specifying the workspace content and packages are contained in subfolders. An example for this structure is shown here: https://github.com/serde-rs/serde/blob/master/Cargo.toml
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
rust-analyzer
A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer] (by rust-analyzer)
For very large projects the structure can get more complicated with packages sorted into multiple subfolders, e.g.: https://github.com/rust-analyzer/rust-analyzer
Related posts
- Security Engineer looking for ways to see if any of my tasks could slowly be ported to Rust or should I just stick with Python.
- Hey rustaceans! I'm interested in learning Rust and I have a few questions before I get started
- Hey, i begin my journey into Rust !
- Does rust have function works like eval?
- no good UI toolkit/framework