mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-13 21:54:42 +00:00
internal: document Cargo.lock maintenance process
This commit is contained in:
parent
aca9004c7e
commit
27b779d1fd
1 changed files with 2 additions and 2 deletions
|
@ -55,9 +55,9 @@ https://www.tedinski.com/2018/02/06/system-boundaries.html
|
||||||
We try to be very conservative with usage of crates.io dependencies.
|
We try to be very conservative with usage of crates.io dependencies.
|
||||||
Don't use small "helper" crates (exception: `itertools` is allowed).
|
Don't use small "helper" crates (exception: `itertools` is allowed).
|
||||||
If there's some general reusable bit of code you need, consider adding it to the `stdx` crate.
|
If there's some general reusable bit of code you need, consider adding it to the `stdx` crate.
|
||||||
|
A useful exercise is to read Cargo.lock and see if some of the *transitive* dependencies do not make sense for rust-analyzer.
|
||||||
|
|
||||||
**Rationale:** keep compile times low, create ecosystem pressure for faster
|
**Rationale:** keep compile times low, create ecosystem pressure for faster compiles, reduce the number of things which might break.
|
||||||
compiles, reduce the number of things which might break.
|
|
||||||
|
|
||||||
## Commit Style
|
## Commit Style
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue