Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-12-26 13:03:31 +00:00
Code Issues Projects Releases Packages Wiki Activity

Fix some grammar / spelling mistakes

Browse source
This commit is contained in:
Jonas Platte 2021-07-26 10:12:41 +02:00
parent 5983d3745a
commit c0107d2ea6
No known key found for this signature in database
GPG key ID: 7D261D771D915378
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
crates/ide_diagnostics/src/lib.rs
View file

@ -43,7 +43,7 @@ mod handlers {
pub(crate) mod unresolved_module;
pub(crate) mod unresolved_proc_macro;
// The handlers bellow are unusual, the implement the diagnostics as well.
// The handlers below are unusual, the implement the diagnostics as well.
pub(crate) mod field_shorthand;
pub(crate) mod useless_braces;
pub(crate) mod unlinked_file;

4
docs/dev/architecture.md
View file

@ -461,9 +461,9 @@ Mind the code--architecture gap: at the moment, we are using fewer feature flags
In Rust, it is easy (often too easy) to add serialization to any type by adding `#[derive(Serialize)]`.
This easiness is misleading -- serializable types impose significant backwards compatability constraints.
If a type is serializable, then it is a part of some IPC boundary.
You often don't control the other side of this boundary, so changing serializable types are hard.
You often don't control the other side of this boundary, so changing serializable types is hard.
For this reason, the types in `ide`, `base_db` and bellow are not serializable by design.
For this reason, the types in `ide`, `base_db` and below are not serializable by design.
If such types need to cross an IPC boundary, then the client of rust-analyzer needs to provide custom, client-specific serialization format.
This isolates backwards compatibility and migration concerns to a specific client.