diff options
| author | Alex Kladov <aleksey.kladov@gmail.com> | 2023-01-13 11:57:02 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-13 11:57:02 +0000 |
| commit | 87315ef5c39647d1ddab66d58153840562dab353 (patch) | |
| tree | faa55fae96e65a5f9f475cb156dd71ba4a3293b5 | |
| parent | aa73366b0b91e1b99a0e6059e7f8dfbcb41cf929 (diff) | |
| download | rust-87315ef5c39647d1ddab66d58153840562dab353.tar.gz rust-87315ef5c39647d1ddab66d58153840562dab353.zip | |
Apply suggestions from code review
Co-authored-by: Laurențiu Nicola <lnicola@users.noreply.github.com>
| -rw-r--r-- | crates/project-model/src/project_json.rs | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/crates/project-model/src/project_json.rs b/crates/project-model/src/project_json.rs index a990fb267a7..319897890fc 100644 --- a/crates/project-model/src/project_json.rs +++ b/crates/project-model/src/project_json.rs @@ -18,10 +18,11 @@ //! Normally, we get this "crate graph" by calling `cargo metadata //! --message-format=json` for each cargo workspace and merging results. This //! works for your typical cargo project, but breaks down for large folks who -//! have a monorepo with an infitine amount of Rust which is build with bazel or +//! have a monorepo with an infinite amount of Rust code which is built with bazel or //! some such. //! -//! To support this use-case, we need to make _something_ configurable. To avoid +//! To support this use case, we need to make _something_ configurable. To avoid +//! a [midlayer mistake](https://lwn.net/Articles/336262/), we allow configuring //! [midlayer mistake](https://lwn.net/Articles/336262/), we allow configuring //! the lowest possible layer. `ProjectJson` is essentially a hook to just set //! that global singleton in-memory data structure. It is optimized for power, |