diff options
| author | Fabian Keller <bluenote10@users.noreply.github.com> | 2021-11-24 10:38:55 +0100 |
|---|---|---|
| committer | Caleb Cartwright <calebcartwright@users.noreply.github.com> | 2021-11-26 16:47:45 -0600 |
| commit | 243cec7a0b9cc0ba3fba6e5ed849b0635f3496db (patch) | |
| tree | 666164588577bff00bbbb08eeced2f01d58697a6 | |
| parent | 4389a4ce49e737915af1f1b27b96b05598a4e388 (diff) | |
| download | rust-243cec7a0b9cc0ba3fba6e5ed849b0635f3496db.tar.gz rust-243cec7a0b9cc0ba3fba6e5ed849b0635f3496db.zip | |
Update README.md
| -rw-r--r-- | README.md | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/README.md b/README.md index b3d21e6fb87..b3a968f0c04 100644 --- a/README.md +++ b/README.md @@ -48,12 +48,11 @@ cargo +nightly fmt ## Limitations Rustfmt tries to work on as much Rust code as possible. Sometimes, the code -doesn't even need to compile! As we approach a 1.0 release we are also looking -to limit areas of instability; in particular, post-1.0, the formatting of most -code should not change as Rustfmt improves. However, there are some things that -Rustfmt can't do or can't do well (and thus where formatting might change -significantly, even post-1.0). We would like to reduce the list of limitations -over time. +doesn't even need to compile! In general, we are looking to limit areas of +instability; in particular, post-1.0, the formatting of most code should not +change as Rustfmt improves. However, there are some things that Rustfmt can't +do or can't do well (and thus where formatting might change significantly, +even post-1.0). We would like to reduce the list of limitations over time. The following list enumerates areas where Rustfmt does not work or where the stability guarantees do not apply (we don't make a distinction between the two |