Lines Matching full:rustfmt

16 //! well-formatted source code. In contrast to rustfmt, this library is intended
19 //! Rustfmt prioritizes high-quality output that is impeccable enough that you'd
22 //! that is hard to format (for example [rustfmt#3697], and there are dozens
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 //! output lines come out identical between rustfmt's formatting and this
48 //! pretty-printer built into rustc, and rustfmt. The sections below go into
51 //! | | prettyplease | rustc | rustfmt |
54 //! | idiomatic modern formatting ("locally indistinguishable from rustfmt") | �� | ❌ | �� |
65 //! # Comparison to rustfmt
69 //! - [output.rustfmt.rs](https://github.com/dtolnay/prettyplease/blob/0.1.0/examples/output.rustfm…
72 //! impossible to tell — **except** for line 435 in the rustfmt output,
73 //! which is more than 1000 characters long because rustfmt just gave up
91 //! This is a pretty typical manifestation of rustfmt bailing out in generated
93 //! manifestation is that you're working on some code, running rustfmt on save
96 //! or semicolon, and run rustfmt to check your suspicion. Nope, it doesn't get
97 //! cleaned up — rustfmt is just not formatting the part of the file you
104 //! Separately, rustfmt can be problematic to integrate into projects. It's
108 //! publishing your crate to crates.io also. You can shell out to a `rustfmt`
109 //! binary, but that'll be whatever rustfmt version is installed on each
172 //! The snippets above are clearly different from modern rustfmt style. In
174 //! indistinguishable from rustfmt-formatted code.
246 //! rustfmt-compatible formatting for all of Rust's syntax tree nodes is a fun
275 //! well-formatted Rust code that is locally indistinguishable from rustfmt's
279 //! idiomatically formattted by rustfmt, that is not the case. Trailing commas