Lines Matching full:rustfmt

16 well-formatted source code. In contrast to rustfmt, this library is intended to
19 Rustfmt prioritizes high-quality output that is impeccable enough that you'd be
22 hard to format (for example [rustfmt#3697], and there are dozens more issues
28 [rustfmt#3697]: https://github.com/rust-lang/rustfmt/issues/3697
31 structures that can deliver about 95% of the quality of rustfmt-formatted
33 lines come out identical between rustfmt's formatting and this crate's. The rest
47 pretty-printer built into rustc, and rustfmt. The sections below go into more
50 | | prettyplease | rustc | rustfmt |
53 | idiomatic modern formatting ("locally indistinguishable from rustfmt") | �� | ❌ | �� |
64 ## Comparison to rustfmt
68 - [output.rustfmt.rs](https://github.com/dtolnay/prettyplease/blob/0.1.0/examples/output.rustfmt.rs)
71 impossible to tell — **except** for line 435 in the rustfmt output, which
72 is more than 1000 characters long because rustfmt just gave up formatting that
88 This is a pretty typical manifestation of rustfmt bailing out in generated code
90 that you're working on some code, running rustfmt on save like a conscientious
92 intentional formatting issue, like a stray indent or semicolon, and run rustfmt
93 to check your suspicion. Nope, it doesn't get cleaned up — rustfmt is just
100 Separately, rustfmt can be problematic to integrate into projects. It's written
104 to crates.io also. You can shell out to a `rustfmt` binary, but that'll be
105 whatever rustfmt version is installed on each developer's system (if any), which
160 The snippets above are clearly different from modern rustfmt style. In contrast,
162 from rustfmt-formatted code.
231 breaks and greedy inconsistent breaks) to yield rustfmt-compatible formatting
260 well-formatted Rust code that is locally indistinguishable from rustfmt's style.
264 formattted by rustfmt, that is not the case. Trailing commas are one example;