Expand description
In rust-analyzer, we maintain a strict separation between pure abstract semantic project model and a concrete model of a particular build system.
Pure model is represented by the [base_db::CrateGraph
] from another crate.
In this crate, we are concerned with “real world” project models.
Specifically, here we have a representation for a Cargo project
(CargoWorkspace
) and for manually specified layout (ProjectJson
).
Roughly, the things we do here are:
- Project discovery (where’s the relevant Cargo.toml for the current dir).
- Custom build steps (
build.rs
code generation and compilation of procedural macros). - Lowering of concrete model to a [
base_db::CrateGraph
]
Re-exports§
pub use crate::project_json::ProjectJson;
pub use crate::project_json::ProjectJsonData;
Modules§
- project_
json rust-project.json
file format.- toolchain_
info
Structs§
- Cargo
Config - Cargo
Metadata Config - Cargo
Workspace CargoWorkspace
represents the logical structure of, well, a Cargo workspace. It pretty closely mirrorscargo metadata
output.- CfgOverrides
- A set of cfg-overrides per crate.
- Manifest
Path - More or less
AbsPathBuf
with non-None parent. - Metadata
- Starting point for metadata returned by
cargo metadata
- Package
Data - Information associated with a cargo crate
- Package
Dependency - Package
Root PackageRoot
describes a package root folder. Which may be an external dependency, or a member of the current workspace.- Project
Json From Command - Project
Workspace - Sysroot
- Target
Data - Information associated with a package’s target
- Workspace
Build Scripts - Output of the build script and proc-macro building steps for a workspace.
Enums§
- Cargo
Features - Invocation
Strategy - Project
Manifest - Project
Workspace Kind - Rust
LibSource - Describes how to set the rustc source directory.
- Rust
Source Workspace Config - Target
Kind