rustfmt
rustfmt, a tool to format Rust code
| Type | object |
|---|---|
| File match |
rustfmt.toml
|
| Schema URL | https://catalog.lintel.tools/schemas/rust/rustfmt/latest.json |
| Source | https://www.schemastore.org/rustfmt.json |
Validate with Lintel
npx @lintel/lintel check
rustfmt configurations
Properties
Maximum width of an array literal before falling back to vertical formatting.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for array_width will take precedence.
See also max_width and use_small_heuristics
Maximum width of the args of a function-like attributes before falling back to vertical formatting.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for attr_fn_like_width will take precedence.
See also max_width and use_small_heuristics
Where to put a binary operator when a binary expression goes multiline.
Stable: No (tracking issue: #3368)
"Front" (default):
fn main() {
let or = foofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoo
|| barbarbarbarbarbarbarbarbarbarbarbarbarbarbarbar;
let sum = 123456789012345678901234567890
+ 123456789012345678901234567890
+ 123456789012345678901234567890;
let range = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
..bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb;
}
"Back":
fn main() {
let or = foofoofoofoofoofoofoofoofoofoofoofoofoofoofoofoo ||
barbarbarbarbarbarbarbarbarbarbarbarbarbarbarbar;
let sum = 123456789012345678901234567890 +
123456789012345678901234567890 +
123456789012345678901234567890;
let range = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa..
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb;
}
Minimum number of blank lines which must be put between items. If two items have fewer blank lines between them, additional blank lines are inserted.
Possible values: unsigned integer
Stable: No (tracking issue: #3382)
Example
Original Code (rustfmt will not change it with the default value of 0):
#![rustfmt::skip]
fn foo() {
println!("a");
}
fn bar() {
println!("b");
println!("c");
}
1
fn foo() {
println!("a");
}
fn bar() {
println!("b");
println!("c");
}
Maximum number of blank lines which can be put between items. If more than this number of consecutive empty lines are found, they are trimmed down to match this integer.
Possible values: any non-negative integer
Stable: No (tracking issue: #3381)
Example
Original Code:
#![rustfmt::skip]
fn foo() {
println!("a");
}
fn bar() {
println!("b");
println!("c");
}
1 (default):
fn foo() {
println!("a");
}
fn bar() {
println!("b");
println!("c");
}
2:
fn foo() {
println!("a");
}
fn bar() {
println!("b");
println!("c");
}
See also: blank_lines_lower_bound
Brace style for items
Stable: No (tracking issue: #3376)
Functions
"SameLineWhere" (default):
fn lorem() {
// body
}
fn lorem(ipsum: usize) {
// body
}
fn lorem<T>(ipsum: T)
where
T: Add + Sub + Mul + Div,
{
// body
}
"AlwaysNextLine":
fn lorem()
{
// body
}
fn lorem(ipsum: usize)
{
// body
}
fn lorem<T>(ipsum: T)
where
T: Add + Sub + Mul + Div,
{
// body
}
"PreferSameLine":
fn lorem() {
// body
}
fn lorem(ipsum: usize) {
// body
}
fn lorem<T>(ipsum: T)
where
T: Add + Sub + Mul + Div, {
// body
}
Structs and enums
"SameLineWhere" (default):
struct Lorem {
ipsum: bool,
}
struct Dolor<T>
where
T: Eq,
{
sit: T,
}
"AlwaysNextLine":
struct Lorem
{
ipsum: bool,
}
struct Dolor<T>
where
T: Eq,
{
sit: T,
}
"PreferSameLine":
struct Lorem {
ipsum: bool,
}
struct Dolor<T>
where
T: Eq, {
sit: T,
}
Maximum width of a chain to fit on one line.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for chain_width will take precedence.
See also max_width and use_small_heuristics
Whether to use colored output or not.
Stable: No (tracking issue: #3385)
Combine control expressions with function calls.
Stable: No (tracking issue: #3369)
true (default):
fn example() {
// If
foo!(if x {
foo();
} else {
bar();
});
// IfLet
foo!(if let Some(..) = x {
foo();
} else {
bar();
});
// While
foo!(while x {
foo();
bar();
});
// WhileLet
foo!(while let Some(..) = x {
foo();
bar();
});
// ForLoop
foo!(for x in y {
foo();
bar();
});
// Loop
foo!(loop {
foo();
bar();
});
}
false:
fn example() {
// If
foo!(
if x {
foo();
} else {
bar();
}
);
// IfLet
foo!(
if let Some(..) = x {
foo();
} else {
bar();
}
);
// While
foo!(
while x {
foo();
bar();
}
);
// WhileLet
foo!(
while let Some(..) = x {
foo();
bar();
}
);
// ForLoop
foo!(
for x in y {
foo();
bar();
}
);
// Loop
foo!(
loop {
foo();
bar();
}
);
}
Maximum length of comments. No effect unless wrap_comments = true.
Possible values: any positive integer
Stable: No (tracking issue: #3349)
Note: A value of 0 results in wrap_comments being applied regardless of a line's width.
80 (default; comments shorter than comment_width):
// Lorem ipsum dolor sit amet, consectetur adipiscing elit.
60 (comments longer than comment_width):
// Lorem ipsum dolor sit amet,
// consectetur adipiscing elit.
See also wrap_comments.
Replace strings of _ wildcards by a single .. in tuple patterns
Stable: No (tracking issue: #3384)
false (default):
fn main() {
let (lorem, ipsum, _, _) = (1, 2, 3, 4);
let (lorem, ipsum, ..) = (1, 2, 3, 4);
}
true:
fn main() {
let (lorem, ipsum, ..) = (1, 2, 3, 4);
}
Brace style for control flow constructs
Stable: No (tracking issue: #3377)
"AlwaysSameLine" (default):
fn main() {
if lorem {
println!("ipsum!");
} else {
println!("dolor!");
}
}
"AlwaysNextLine":
fn main() {
if lorem
{
println!("ipsum!");
}
else
{
println!("dolor!");
}
}
"ClosingNextLine":
fn main() {
if lorem {
println!("ipsum!");
}
else {
println!("dolor!");
}
}
Specifies which edition is used by the parser.
Stable: Yes
The edition option determines the Rust language edition used for parsing the code. This is important for syntax compatibility but does not directly control formatting behavior (see style_edition).
When running cargo fmt, the edition is automatically read from the Cargo.toml file. However, when running rustfmt directly the edition defaults to 2015 if not explicitly configured. For consistent parsing between rustfmt and cargo fmt you should configure the edition.
For example in your rustfmt.toml file:
edition = "2018"
Alternatively, you can use the --edition flag when running rustfmt directly.
Put empty-body functions and impls on a single line
Stable: No (tracking issue: #3356)
true (default):
fn lorem() {}
impl Lorem {}
false:
fn lorem() {
}
impl Lorem {
}
See also brace_style, control_brace_style.
The maximum length of enum variant having discriminant, that gets vertically aligned with others. Variants without discriminants would be ignored for the purpose of alignment.
Note that this is not how much whitespace is inserted, but instead the longest variant name that doesn't get ignored when aligning.
Possible values: any positive integer
Stable: No (tracking issue: #3372)
0 (default):
enum Foo {
A = 0,
Bb = 1,
RandomLongVariantGoesHere = 10,
Ccc = 71,
}
enum Bar {
VeryLongVariantNameHereA = 0,
VeryLongVariantNameHereBb = 1,
VeryLongVariantNameHereCcc = 2,
}
20:
enum Foo {
A = 0,
Bb = 1,
RandomLongVariantGoesHere = 10,
Ccc = 2,
}
enum Bar {
VeryLongVariantNameHereA = 0,
VeryLongVariantNameHereBb = 1,
VeryLongVariantNameHereCcc = 2,
}
Error if Rustfmt is unable to get all lines within max_width, except for comments and string
literals. If this happens, then it is a bug in Rustfmt. You might be able to work around the bug by
refactoring your code to avoid long/complex expressions, usually by extracting a local variable or
using a shorter name.
Stable: No (tracking issue: #3391)
See also max_width.
Error if unable to get comments or string literals within max_width, or they are left with
trailing whitespaces.
Stable: No (tracking issue: #3392)
This option is deprecated and has been renamed to fn_params_layout to better communicate that
it affects the layout of parameters in function signatures.
Stable: Yes
"Tall" (default):
trait Lorem {
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet);
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet) {
// body
}
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
) {
// body
}
}
"Compressed":
trait Lorem {
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet);
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet) {
// body
}
fn lorem(
ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet, consectetur: Consectetur,
adipiscing: Adipiscing, elit: Elit,
);
fn lorem(
ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet, consectetur: Consectetur,
adipiscing: Adipiscing, elit: Elit,
) {
// body
}
}
"Vertical":
trait Lorem {
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
) {
// body
}
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
) {
// body
}
}
See also fn_params_layout
Maximum width of the args of a function call before falling back to vertical formatting.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for fn_call_width will take precedence.
See also max_width and use_small_heuristics
Control the layout of parameters in function signatures.
Stable: Yes
"Tall" (default):
trait Lorem {
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet);
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet) {
// body
}
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
) {
// body
}
}
"Compressed":
trait Lorem {
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet);
fn lorem(ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet) {
// body
}
fn lorem(
ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet, consectetur: Consectetur,
adipiscing: Adipiscing, elit: Elit,
);
fn lorem(
ipsum: Ipsum, dolor: Dolor, sit: Sit, amet: Amet, consectetur: Consectetur,
adipiscing: Adipiscing, elit: Elit,
) {
// body
}
}
"Vertical":
trait Lorem {
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
) {
// body
}
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
);
fn lorem(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
consectetur: Consectetur,
adipiscing: Adipiscing,
elit: Elit,
) {
// body
}
}
Put single-expression functions on a single line
Stable: No (tracking issue: #3358)
false (default):
fn lorem() -> usize {
42
}
fn lorem() -> usize {
let ipsum = 42;
ipsum
}
true:
fn lorem() -> usize { 42 }
fn lorem() -> usize {
let ipsum = 42;
ipsum
}
See also control_brace_style.
Always print the abi for extern items
Stable: Yes
Note: Non-"C" ABIs are always printed. If false then "C" is removed.
true (default):
extern "C" {
pub static lorem: c_int;
}
false:
extern {
pub static lorem: c_int;
}
Force multiline closure and match arm bodies to be wrapped in a block
Stable: No (tracking issue: #3374)
false (default):
fn main() {
result.and_then(|maybe_value| match maybe_value {
None => foo(),
Some(value) => bar(),
});
match lorem {
None => |ipsum| {
println!("Hello World");
},
Some(dolor) => foo(),
}
}
true:
fn main() {
result.and_then(|maybe_value| {
match maybe_value {
None => foo(),
Some(value) => bar(),
}
});
match lorem {
None => {
|ipsum| {
println!("Hello World");
}
}
Some(dolor) => foo(),
}
}
Format code snippet included in doc comments.
Stable: No (tracking issue: #3348)
false (default):
/// Adds one to the number given.
///
/// # Examples
///
/// ```rust
/// let five=5;
///
/// assert_eq!(
/// 6,
/// add_one(5)
/// );
/// # fn add_one(x: i32) -> i32 {
/// # x + 1
/// # }
/// ```
fn add_one(x: i32) -> i32 {
x + 1
}
true
/// Adds one to the number given.
///
/// # Examples
///
/// ```rust
/// let five = 5;
///
/// assert_eq!(6, add_one(5));
/// # fn add_one(x: i32) -> i32 {
/// # x + 1
/// # }
/// ```
fn add_one(x: i32) -> i32 {
x + 1
}
Max width for code snippets included in doc comments. Only used if format_code_in_doc_comments is true.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: No (tracking issue: #5359)
Format generated files. A file is considered generated if any of the first several lines contain a @generated comment marker. The number of lines to check is configured by generated_marker_line_search_limit.
By default, generated files are reformatted, i. e. @generated marker is ignored.
This option is currently ignored for stdin (@generated in stdin is ignored.)
Stable: No (tracking issue: #5080)
Number of lines to check for a @generated pragma header, starting from the top of the file. Setting this value to 0 will treat all files as non-generated. Whenformat_generated_files is true, this option has no effect.
Possible values: any positive integer
Stable: No (tracking issue: #5080)
See also format_generated_files link here.
Format the metavariable matching patterns in macros.
Stable: No (tracking issue: #3354)
false (default):
macro_rules! foo {
($a: ident : $b: ty) => {
$a(42): $b;
};
($a: ident $b: ident $c: ident) => {
$a = $b + $c;
};
}
true:
macro_rules! foo {
($a:ident : $b:ty) => {
$a(42): $b;
};
($a:ident $b:ident $c:ident) => {
$a = $b + $c;
};
}
See also format_macro_bodies.
Format the bodies of declarative macro definitions.
Stable: No (tracking issue: #3355)
true (default):
macro_rules! foo {
($a: ident : $b: ty) => {
$a(42): $b;
};
($a: ident $b: ident $c: ident) => {
$a = $b + $c;
};
}
false:
macro_rules! foo {
($a: ident : $b: ty) => { $a(42): $b; };
($a: ident $b: ident $c: ident) => { $a=$b+$c; };
}
See also format_macro_matchers.
Skip formatting the bodies of macro invocations with the following names.
rustfmt will not format any macro invocation for macros with names set in this list. Including the special value "*" will prevent any macro invocations from being formatted.
Note: This option does not have any impact on how rustfmt formats macro definitions.
Possible values: a list of macro name idents, ["name_0", "name_1", ..., "*"]
Stable: No (tracking issue: #5346)
[] (default):
rustfmt will follow its standard approach to formatting macro invocations.
No macro invocations will be skipped based on their name. More information about rustfmt's standard macro invocation formatting behavior can be found in #5437.
lorem!(
const _: u8 = 0;
);
ipsum!(
const _: u8 = 0;
);
["lorem"]:
The named macro invocations will be skipped.
lorem!(
const _: u8 = 0;
);
ipsum!(
const _: u8 = 0;
);
["*"]:
The special selector * will skip all macro invocations.
lorem!(
const _: u8 = 0;
);
ipsum!(
const _: u8 = 0;
);
[]
Format string literals where necessary
Stable: No (tracking issue: #3353)
false (default):
fn main() {
let lorem = "ipsum dolor sit amet consectetur adipiscing elit lorem ipsum dolor sit amet consectetur adipiscing";
}
true:
fn main() {
let lorem = "ipsum dolor sit amet consectetur adipiscing elit lorem ipsum dolor sit amet \
consectetur adipiscing";
}
See also max_width.
Use tab characters for indentation, spaces for alignment
Stable: Yes
false (default):
fn lorem() -> usize {
42 // spaces before 42
}
true:
fn lorem() -> usize {
42 // tabs before 42
}
See also: tab_spaces.
Control the case of the letters in hexadecimal literal values
Stable: No (tracking issue: #5081)
Control the presence of trailing zero in floating-point literal values
Stable: No (tracking issue: #6471)
Preserve (default):
Leave the literal as-is.
fn main() {
let values = [1.0, 2., 3.0e10, 4f32];
}
Always:
Add a trailing zero to the literal:
fn main() {
let values = [1.0, 2.0, 3.0e10, 4.0f32];
}
IfNoPostfix:
Add a trailing zero by default. If the literal contains an exponent or a suffix, the zero and the preceding period are removed:
fn main() {
let values = [1.0, 2.0, 3e10, 4f32];
}
Never:
Remove the trailing zero. If the literal contains an exponent or a suffix, the preceding period is also removed:
fn main() {
let values = [1., 2., 3e10, 4f32];
}
This option is deprecated and has been renamed to show_parse_errors to avoid confusion around the double negative default of hide_parse_errors=false.
Stable: No (tracking issue: #3390)
Show parse errors if the parser failed to parse files.
Stable: No (tracking issue: #5977)
Skip formatting files and directories that match the specified pattern.
The pattern format is the same as .gitignore. Be sure to use Unix/forwardslash / style paths. This path style will work on all platforms. Windows style paths with backslashes \ are not supported.
Default value: format every file
Possible values: See an example below
Stable: No (tracking issue: #3395)
Example
If you want to ignore specific files, put the following to your config file:
ignore = [
"src/types.rs",
"src/foo/bar.rs",
]
If you want to ignore every file under examples/, put the following to your config file:
ignore = [
"examples",
]
If you want to ignore every file under the directory where you put your rustfmt.toml:
ignore = ["/"]
If you want to allow specific paths that would otherwise be ignored, prefix those paths with a !:
ignore = ["bar_dir/*", "!bar_dir/*/what.rs"]
In this case, all files under bar_dir will be ignored, except files like bar_dir/sub/what.rs
or bar_dir/another/what.rs.
Indent style of imports
Stable: No (tracking issue: #3360)
"Block" (default):
use foo::{
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy,
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz,
};
"Visual":
use foo::{xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy,
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz};
See also: imports_layout.
Item layout inside a imports block
Stable: No (tracking issue: #3361)
"Mixed" (default):
use foo::{xxxxxxxxxxxxxxxxxx, yyyyyyyyyyyyyyyyyy, zzzzzzzzzzzzzzzzzz};
use foo::{
aaaaaaaaaaaaaaaaaa, bbbbbbbbbbbbbbbbbb, cccccccccccccccccc, dddddddddddddddddd,
eeeeeeeeeeeeeeeeee, ffffffffffffffffff,
};
"Horizontal":
Note: This option forces all imports onto one line and may exceed max_width.
use foo::{xxx, yyy, zzz};
use foo::{aaa, bbb, ccc, ddd, eee, fff};
"HorizontalVertical":
use foo::{xxxxxxxxxxxxxxxxxx, yyyyyyyyyyyyyyyyyy, zzzzzzzzzzzzzzzzzz};
use foo::{
aaaaaaaaaaaaaaaaaa,
bbbbbbbbbbbbbbbbbb,
cccccccccccccccccc,
dddddddddddddddddd,
eeeeeeeeeeeeeeeeee,
ffffffffffffffffff,
};
"Vertical":
use foo::{
xxx,
yyy,
zzz,
};
use foo::{
aaa,
bbb,
ccc,
ddd,
eee,
fff,
};
Indent on expressions or items.
Stable: No (tracking issue: #3346)
Array
"Block" (default):
fn main() {
let lorem = vec![
"ipsum",
"dolor",
"sit",
"amet",
"consectetur",
"adipiscing",
"elit",
];
}
"Visual":
fn main() {
let lorem = vec!["ipsum",
"dolor",
"sit",
"amet",
"consectetur",
"adipiscing",
"elit"];
}
Control flow
"Block" (default):
fn main() {
if lorem_ipsum
&& dolor_sit
&& amet_consectetur
&& lorem_sit
&& dolor_consectetur
&& amet_ipsum
&& lorem_consectetur
{
// ...
}
}
"Visual":
fn main() {
if lorem_ipsum
&& dolor_sit
&& amet_consectetur
&& lorem_sit
&& dolor_consectetur
&& amet_ipsum
&& lorem_consectetur
{
// ...
}
}
See also: control_brace_style.
Function arguments
"Block" (default):
fn lorem() {}
fn lorem(ipsum: usize) {}
fn lorem(
ipsum: usize,
dolor: usize,
sit: usize,
amet: usize,
consectetur: usize,
adipiscing: usize,
elit: usize,
) {
// body
}
"Visual":
fn lorem() {}
fn lorem(ipsum: usize) {}
fn lorem(ipsum: usize,
dolor: usize,
sit: usize,
amet: usize,
consectetur: usize,
adipiscing: usize,
elit: usize) {
// body
}
Function calls
"Block" (default):
fn main() {
lorem(
"lorem",
"ipsum",
"dolor",
"sit",
"amet",
"consectetur",
"adipiscing",
"elit",
);
}
"Visual":
fn main() {
lorem("lorem",
"ipsum",
"dolor",
"sit",
"amet",
"consectetur",
"adipiscing",
"elit");
}
Generics
"Block" (default):
fn lorem<
Ipsum: Eq = usize,
Dolor: Eq = usize,
Sit: Eq = usize,
Amet: Eq = usize,
Adipiscing: Eq = usize,
Consectetur: Eq = usize,
Elit: Eq = usize,
>(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
adipiscing: Adipiscing,
consectetur: Consectetur,
elit: Elit,
) -> T {
// body
}
"Visual":
fn lorem<Ipsum: Eq = usize,
Dolor: Eq = usize,
Sit: Eq = usize,
Amet: Eq = usize,
Adipiscing: Eq = usize,
Consectetur: Eq = usize,
Elit: Eq = usize>(
ipsum: Ipsum,
dolor: Dolor,
sit: Sit,
amet: Amet,
adipiscing: Adipiscing,
consectetur: Consectetur,
elit: Elit)
-> T {
// body
}
Struct
"Block" (default):
fn main() {
let lorem = Lorem {
ipsum: dolor,
sit: amet,
};
}
"Visual":
fn main() {
let lorem = Lorem { ipsum: dolor,
sit: amet };
}
See also: struct_lit_single_line, indent_style.
Where predicates
"Block" (default):
fn lorem<Ipsum, Dolor, Sit, Amet>() -> T
where
Ipsum: Eq,
Dolor: Eq,
Sit: Eq,
Amet: Eq,
{
// body
}
"Visual":
fn lorem<Ipsum, Dolor, Sit, Amet>() -> T
where Ipsum: Eq,
Dolor: Eq,
Sit: Eq,
Amet: Eq
{
// body
}
Write an item and its attribute on the same line if their combined width is below a threshold
Possible values: any positive integer
Stable: No (tracking issue: #3343)
Example
0 (default):
#[cfg(feature = "alloc")]
use core::slice;
50:
#[cfg(feature = "alloc")] use core::slice;
Controls whether arm bodies are wrapped in cases where the first line of the body cannot fit on the same line as the => operator.
The Style Guide requires that bodies are block wrapped by default if a line break is required after the =>, but this option can be used to disable that behavior to prevent wrapping arm bodies in that event, so long as the body contains neither multiple statements nor line comments.
Stable: No (tracking issue: #3373)
true (default):
fn main() {
match lorem {
ipsum => {
foooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo(x)
}
dolor => println!("{}", sit),
sit => foo(
"foooooooooooooooooooooooo",
"baaaaaaaaaaaaaaaaaaaaaaaarr",
"baaaaaaaaaaaaaaaaaaaazzzzzzzzzzzzz",
"qqqqqqqqquuuuuuuuuuuuuuuuuuuuuuuuuuxxx",
),
}
}
false:
fn main() {
match lorem {
lorem =>
foooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo(x),
ipsum => println!("{}", sit),
sit => foo(
"foooooooooooooooooooooooo",
"baaaaaaaaaaaaaaaaaaaaaaaarr",
"baaaaaaaaaaaaaaaaaaaazzzzzzzzzzzzz",
"qqqqqqqqquuuuuuuuuuuuuuuuuuuuuuuuuuxxx",
),
}
}
See also: match_block_trailing_comma.
Controls whether to include a leading pipe on match arms
Stable: Yes
Never (default):
// Leading pipes are removed from this:
// fn foo() {
// match foo {
// | "foo" | "bar" => {}
// | "baz"
// | "something relatively long"
// | "something really really really realllllllllllllly long" => println!("x"),
// | "qux" => println!("y"),
// _ => {}
// }
// }
// Becomes
fn foo() {
match foo {
"foo" | "bar" => {}
"baz"
| "something relatively long"
| "something really really really realllllllllllllly long" => println!("x"),
"qux" => println!("y"),
_ => {}
}
}
Always:
// Leading pipes are emitted on all arms of this:
// fn foo() {
// match foo {
// "foo" | "bar" => {}
// "baz"
// | "something relatively long"
// | "something really really really realllllllllllllly long" => println!("x"),
// "qux" => println!("y"),
// _ => {}
// }
// }
// Becomes:
fn foo() {
match foo {
| "foo" | "bar" => {}
| "baz"
| "something relatively long"
| "something really really really realllllllllllllly long" => println!("x"),
| "qux" => println!("y"),
| _ => {}
}
}
Preserve:
fn foo() {
match foo {
| "foo" | "bar" => {}
| "baz"
| "something relatively long"
| "something really really really realllllllllllllly long" => println!("x"),
| "qux" => println!("y"),
_ => {}
}
match baz {
"qux" => {}
"foo" | "bar" => {}
_ => {}
}
}
Controls whether match arms are indented. If disabled, match arms will be formatted at the same indentation level as the outer match statement. Meaning that match blocks will only be indented once, not twice.
Stable: No (tracking issue: #6533)
true (default):
fn main() {
match value {
Enum::A => {
let mut work = first();
work += second();
}
Enum::B => short_work(),
}
}
false:
fn main() {
match value {
Enum::A => {
let mut work = first();
work += second();
}
Enum::B => short_work(),
}
}
Put a trailing comma after a block based match arm (non-block arms are not affected)
Stable: Yes
false (default):
fn main() {
match lorem {
Lorem::Ipsum => {
println!("ipsum");
}
Lorem::Dolor => println!("dolor"),
}
}
true:
fn main() {
match lorem {
Lorem::Ipsum => {
println!("ipsum");
},
Lorem::Dolor => println!("dolor"),
}
}
See also: trailing_comma, match_arm_blocks.
Maximum width of each line
Possible values: any positive integer
Stable: Yes
See also error_on_line_overflow.
Merge multiple derives into a single one.
Stable: Yes
true (default):
#[derive(Eq, PartialEq, Debug, Copy, Clone)]
pub enum Foo {}
false:
#[derive(Eq, PartialEq, Debug, Copy, Clone)]
pub enum Bar {}
#[derive(Eq, PartialEq)]
#[derive(Debug)]
#[derive(Copy, Clone)]
pub enum Foo {}
Controls how imports are structured in use statements. Imports will be merged or split to the configured level of granularity.
Similar to other import related configuration options, this option operates within the bounds of user-defined groups of imports. See group_imports for more information on import groups.
Note that rustfmt will not modify the granularity of imports containing comments if doing so could potentially lose or misplace said comments.
Stable: No (tracking issue: #4991)
Preserve (default):
Do not change the granularity of any imports and preserve the original structure written by the developer.
use foo::b;
use foo::b::{f, g};
use foo::{a, c, d::e};
use qux::{h, i};
Crate:
Merge imports from the same crate into a single use statement. Conversely, imports from different crates are split into separate statements.
use foo::{
a, b,
b::{f, g},
c,
d::e,
};
use qux::{h, i};
Module:
Merge imports from the same module into a single use statement. Conversely, imports from different modules are split into separate statements.
use foo::b::{f, g};
use foo::d::e;
use foo::{a, b, c};
use qux::{h, i};
Item:
Flatten imports so that each has its own use statement.
use foo::a;
use foo::b;
use foo::b::f;
use foo::b::g;
use foo::c;
use foo::d::e;
use qux::h;
use qux::i;
One:
Merge all imports into a single use statement as long as they have the same visibility.
pub use foo::{x, y};
use {
bar::{
a,
b::{self, f, g},
c,
d::e,
},
qux::{h, i},
};
This option is deprecated. Use imports_granularity = "Crate" instead.
Stable: undefined
false (default):
use foo::{a, c, d};
use foo::{b, g};
use foo::{e, f};
true:
use foo::{a, b, c, d, e, f, g};
Unix or Windows line endings
Stable: Yes
Auto (default):
The newline style is detected automatically on a per-file basis. Files with mixed line endings will be converted to the first detected line ending style.
Native
Line endings will be converted to \r\n on Windows and \n on all
other platforms.
Unix
Line endings will be converted to \n.
Windows
Line endings will be converted to \r\n.
Convert /* */ comments to // comments where possible
Stable: No (tracking issue: #3350)
false (default):
// Lorem ipsum:
fn dolor() -> usize {}
/* sit amet: */
fn adipiscing() -> usize {}
true:
// Lorem ipsum:
fn dolor() -> usize {}
// sit amet:
fn adipiscing() -> usize {}
Convert #![doc] and #[doc] attributes to //! and /// doc comments.
Stable: No (tracking issue: #3351)
false (default):
#![doc = "Example documentation"]
#[doc = "Example item documentation"]
pub enum Bar {}
/// Example item documentation
pub enum Foo {}
true:
//! Example documentation
/// Example item documentation
pub enum Foo {}
When structs, slices, arrays, and block/array-like macros are used as the last argument in an expression list, allow them to overflow (like blocks/closures) instead of being indented on a new line.
Stable: No (tracking issue: #3370)
false (default):
fn example() {
foo(ctx, |param| {
action();
foo(param)
});
foo(
ctx,
Bar {
x: value,
y: value2,
},
);
foo(
ctx,
&[
MAROON_TOMATOES,
PURPLE_POTATOES,
ORGANE_ORANGES,
GREEN_PEARS,
RED_APPLES,
],
);
foo(
ctx,
vec![
MAROON_TOMATOES,
PURPLE_POTATOES,
ORGANE_ORANGES,
GREEN_PEARS,
RED_APPLES,
],
);
}
true:
fn example() {
foo(ctx, |param| {
action();
foo(param)
});
foo(ctx, Bar {
x: value,
y: value2,
});
foo(ctx, &[
MAROON_TOMATOES,
PURPLE_POTATOES,
ORGANE_ORANGES,
GREEN_PEARS,
RED_APPLES,
]);
foo(ctx, vec![
MAROON_TOMATOES,
PURPLE_POTATOES,
ORGANE_ORANGES,
GREEN_PEARS,
RED_APPLES,
]);
}
Remove nested parens.
Stable: Yes
true (default):
fn main() {
(foo());
}
false:
fn main() {
(foo());
((((foo()))));
}
Reorder impl items. type and const are put first, then macros and methods.
Stable: No (tracking issue: #3363)
false (default)
struct Dummy;
impl Iterator for Dummy {
fn next(&mut self) -> Option<Self::Item> {
None
}
type Item = i32;
}
impl Iterator for Dummy {
type Item = i32;
fn next(&mut self) -> Option<Self::Item> {
None
}
}
true
struct Dummy;
impl Iterator for Dummy {
type Item = i32;
fn next(&mut self) -> Option<Self::Item> {
None
}
}
Reorder import and extern crate statements alphabetically in groups (a group is separated by a newline).
Stable: Yes
true (default):
use dolor;
use ipsum;
use lorem;
use sit;
false:
use lorem;
use ipsum;
use dolor;
use sit;
Controls the strategy for how consecutive imports are grouped together.
Controls the strategy for grouping sets of consecutive imports. Imports may contain newlines between imports and still be grouped together as a single set, but other statements between imports will result in different grouping sets.
Stable: No (tracking issue: #5083)
Each set of imports (one or more use statements, optionally separated by newlines) will be formatted independently. Other statements such as mod ... or extern crate ... will cause imports to not be grouped together.
Preserve (default):
Preserve the source file's import groups.
use super::update::convert_publish_payload;
use chrono::Utc;
use alloc::alloc::Layout;
use juniper::{FieldError, FieldResult};
use uuid::Uuid;
use std::sync::Arc;
use broker::database::PooledConnection;
use super::schema::{Context, Payload};
use crate::models::Event;
use core::f32;
StdExternalCrate:
Discard existing import groups, and create three groups for:
std,coreandalloc,- external crates,
self,superandcrateimports.
use alloc::alloc::Layout;
use core::f32;
use std::sync::Arc;
use broker::database::PooledConnection;
use chrono::Utc;
use juniper::{FieldError, FieldResult};
use uuid::Uuid;
use super::schema::{Context, Payload};
use super::update::convert_publish_payload;
use crate::models::Event;
One:
Discard existing import groups, and create a single group for everything
use super::schema::{Context, Payload};
use super::update::convert_publish_payload;
use crate::models::Event;
use alloc::alloc::Layout;
use broker::database::PooledConnection;
use chrono::Utc;
use core::f32;
use juniper::{FieldError, FieldResult};
use std::sync::Arc;
use uuid::Uuid;
Reorder mod declarations alphabetically in group.
Stable: Yes
true (default)
mod a;
mod b;
mod dolor;
mod ipsum;
mod lorem;
mod sit;
false
mod b;
mod a;
mod lorem;
mod ipsum;
mod dolor;
mod sit;
Note mod with #[macro_export] will not be reordered since that could change the semantics
of the original source code.
Require a specific version of rustfmt. If you want to make sure that the specific version of rustfmt is used in your CI, use this option.
Possible values: semver compliant values, such as defined on semver.org.
Stable: No (tracking issue: #3386)
Match on exact version:
required_version="1.0.0"
Higher or equal to:
required_version=">=1.0.0"
Lower or equal to:
required_version="<=1.0.0"
New minor or patch versions:
required_version="^1.0.0"
New patch versions:
required_version="~1.0.0"
Wildcard:
required_version="*" # matches any version.
required_version="1.*" # matches any version with the same major version
required_version="1.0.*" # matches any version with the same major and minor version
Multiple versions to match:
A comma separated list of version requirements. The match succeeds when the current rustfmt version matches all version requirements.
The one notable exception is that a wildcard matching any version cannot be used in the list.
For example, *, <1.0.0 will always fail.
Additionally, the version match will always fail if any of the version requirements contradict themselves.
Some examples of contradictory requirements are 1.*, >2.0.0, 1.0.*, >2.0.0 and <1.5.0, >1.10.*.
required_version=">=1.0.0, <2.0.0"
The width threshold for an array element to be considered "short".
The layout of an array is dependent on the length of each of its elements. If the length of every element in an array is below this threshold (all elements are "short") then the array can be formatted in the mixed/compressed style, but if any one element has a length that exceeds this threshold then the array elements will have to be formatted vertically.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
10 (default):
fn main() {
pub const FORMAT_TEST: [u64; 5] = [
0x0000000000000000,
0xaaaaaaaaaaaaaaaa,
0xbbbbbbbbbbbbbbbb,
0xcccccccccccccccc,
0xdddddddddddddddd,
];
}
20:
fn main() {
pub const FORMAT_TEST: [u64; 5] = [
0x0000000000000000, 0xaaaaaaaaaaaaaaaa, 0xbbbbbbbbbbbbbbbb, 0xcccccccccccccccc,
0xdddddddddddddddd,
];
}
See also max_width.
Don't reformat out of line modules
Stable: No (tracking issue: #3389)
Maximum line length for single line if-else expressions. A value of 0 (zero) results in if-else expressions always being broken into multiple lines. Note this occurs when use_small_heuristics is set to Off.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for single_line_if_else_max_width will take precedence.
See also max_width and use_small_heuristics
Maximum line length for single line let-else statements.
See the let-else statement section of the Rust Style Guide for more details on when a let-else statement may be written on a single line.
A value of 0 (zero) means the divergent else block will always be formatted over multiple lines.
Note this occurs when use_small_heuristics is set to Off.
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for single_line_let_else_max_width will take precedence.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
50 (default):
fn main() {
let Some(w) = opt else { return Ok(()) };
let Some(x) = opt else { return };
let Some(y) = opt else {
return;
};
let Some(z) = some_very_very_very_very_long_name else {
return;
};
}
0:
fn main() {
let Some(w) = opt else {
return Ok(());
};
let Some(x) = opt else {
return;
};
let Some(y) = opt else {
return;
};
let Some(z) = some_very_very_very_very_long_name else {
return;
};
}
100:
fn main() {
let Some(w) = opt else { return Ok(()) };
let Some(x) = opt else { return };
let Some(y) = opt else {
return;
};
let Some(z) = some_very_very_very_very_long_name else { return };
}
See also max_width and use_small_heuristics
Leave a space after the colon.
Stable: No (tracking issue: #3366)
true (default):
fn lorem<T: Eq>(t: T) {
let lorem: Dolor = Lorem {
ipsum: dolor,
sit: amet,
};
}
false:
fn lorem<T:Eq>(t:T) {
let lorem:Dolor = Lorem {
ipsum:dolor,
sit:amet,
};
}
See also: space_before_colon.
Leave a space before the colon.
Stable: No (tracking issue: #3365)
false (default):
fn lorem<T: Eq>(t: T) {
let lorem: Dolor = Lorem {
ipsum: dolor,
sit: amet,
};
}
true:
fn lorem<T : Eq>(t : T) {
let lorem : Dolor = Lorem {
ipsum : dolor,
sit : amet,
};
}
See also: space_after_colon.
Put spaces around the .., ..=, and ... range operators
Stable: No (tracking issue: #3367)
false (default):
fn main() {
let lorem = 0..10;
let ipsum = 0..=10;
match lorem {
1..5 => foo(),
_ => bar,
}
match lorem {
1..=5 => foo(),
_ => bar,
}
match lorem {
1...5 => foo(),
_ => bar,
}
}
true:
fn main() {
let lorem = 0 .. 10;
let ipsum = 0 ..= 10;
match lorem {
1 .. 5 => foo(),
_ => bar,
}
match lorem {
1 ..= 5 => foo(),
_ => bar,
}
match lorem {
1 ... 5 => foo(),
_ => bar,
}
}
The maximum diff of width between struct fields to be aligned with each other.
Possible values: any non-negative integer
Stable: No (tracking issue: #3371)
0 (default):
struct Foo {
x: u32,
yy: u32,
zzz: u32,
}
20:
struct Foo {
x: u32,
yy: u32,
zzz: u32,
}
Put small struct literals on a single line
Stable: No (tracking issue: #3357)
true (default):
fn main() {
let lorem = Lorem { foo: bar, baz: ofo };
}
false:
fn main() {
let lorem = Lorem {
foo: bar,
baz: ofo,
};
}
See also: indent_style.
Maximum width in the body of a struct literal before falling back to vertical formatting. A value of 0 (zero) results in struct literals always being broken into multiple lines. Note this occurs when use_small_heuristics is set to Off.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for struct_lit_width will take precedence.
See also max_width, use_small_heuristics, and struct_lit_single_line
Maximum width in the body of a struct variant before falling back to vertical formatting. A value of 0 (zero) results in struct literals always being broken into multiple lines. Note this occurs when use_small_heuristics is set to Off.
Possible values: any positive integer that is less than or equal to the value specified for max_width
Stable: Yes
By default this option is set as a percentage of max_width provided by use_small_heuristics, but a value set directly for struct_variant_width will take precedence.
See also max_width and use_small_heuristics
Controls the edition of the Rust Style Guide to use for formatting (RFC 3338)
Possible values: "2015", "2018", "2021", "2024" (unstable variant)
Stable: No
This option is inferred from the edition if not specified.
See Rust Style Editions for details on formatting differences between style editions.
rustfmt has a default style edition of 2015 while cargo fmt infers the style edition from the edition set in Cargo.toml. This can lead to inconsistencies between rustfmt and cargo fmt if the style edition is not explicitly configured.
To ensure consistent formatting, it is recommended to specify the style_edition in a rustfmt.toml configuration file. For example:
style_edition = "2024"
Alternatively, you can use the --style-edition flag when running rustfmt directly.
Number of spaces per tab
Possible values: any positive integer
Stable: Yes
4 (default):
fn lorem() {
let ipsum = dolor();
let sit = vec![
"amet consectetur adipiscing elit amet",
"consectetur adipiscing elit amet consectetur.",
];
}
2:
fn lorem() {
let ipsum = dolor();
let sit = vec![
"amet consectetur adipiscing elit amet",
"consectetur adipiscing elit amet consectetur.",
];
}
See also: hard_tabs.
How to handle trailing commas for lists
Stable: No (tracking issue: #3379)
"Vertical" (default):
fn main() {
let Lorem { ipsum, dolor, sit } = amet;
let Lorem {
ipsum,
dolor,
sit,
amet,
consectetur,
adipiscing,
} = elit;
}
"Always":
fn main() {
let Lorem { ipsum, dolor, sit, } = amet;
let Lorem {
ipsum,
dolor,
sit,
amet,
consectetur,
adipiscing,
} = elit;
}
"Never":
fn main() {
let Lorem { ipsum, dolor, sit } = amet;
let Lorem {
ipsum,
dolor,
sit,
amet,
consectetur,
adipiscing
} = elit;
}
See also: match_block_trailing_comma.
Add trailing semicolon after break, continue and return
Stable: No (tracking issue: #3378)
true (default):
fn foo() -> usize {
return 0;
}
false:
fn foo() -> usize {
return 0
}
Determines if + or = are wrapped in spaces in the punctuation of types
Stable: No (tracking issue: #3364)
"Wide" (default):
fn lorem<Ipsum: Dolor + Sit = Amet>() {
// body
}
"Compressed":
fn lorem<Ipsum: Dolor+Sit=Amet>() {
// body
}
Enable unstable features on the unstable channel.
Stable: No (tracking issue: #3387)
Use field initialize shorthand if possible.
Stable: Yes
false (default):
struct Foo {
x: u32,
y: u32,
z: u32,
}
fn main() {
let x = 1;
let y = 2;
let z = 3;
let a = Foo { x, y, z };
let b = Foo { x: x, y: y, z: z };
}
true:
struct Foo {
x: u32,
y: u32,
z: u32,
}
fn main() {
let x = 1;
let y = 2;
let z = 3;
let a = Foo { x, y, z };
let b = Foo { x, y, z };
}
This option can be used to simplify the management and bulk updates of the granular width configuration settings (fn_call_width, attr_fn_like_width, struct_lit_width, struct_variant_width, array_width, chain_width, single_line_if_else_max_width), that respectively control when formatted constructs are multi-lined/vertical based on width.
Note that explicitly provided values for the width configuration settings take precedence and override the calculated values determined by use_small_heuristics.
Stable: Yes
Default (default):
When use_small_heuristics is set to Default, the values for the granular width settings are calculated as a ratio of the value for max_width.
The ratios are:
fn_call_width-60%attr_fn_like_width-70%struct_lit_width-18%struct_variant_width-35%array_width-60%chain_width-60%single_line_if_else_max_width-50%single_line_let_else_max_width-50%
For example when max_width is set to 100, the width settings are:
fn_call_width=60attr_fn_like_width=70struct_lit_width=18struct_variant_width=35array_width=60chain_width=60single_line_if_else_max_width=50single_line_let_else_max_width=50
and when max_width is set to 200:
fn_call_width=120attr_fn_like_width=140struct_lit_width=36struct_variant_width=70array_width=120chain_width=120single_line_if_else_max_width=100single_line_let_else_max_width=100
enum Lorem {
Ipsum,
Dolor(bool),
Sit { amet: Consectetur, adipiscing: Elit },
}
fn main() {
lorem(
"lorem",
"ipsum",
"dolor",
"sit",
"amet",
"consectetur",
"adipiscing",
);
let lorem = Lorem {
ipsum: dolor,
sit: amet,
};
let lorem = Lorem { ipsum: dolor };
let lorem = if ipsum { dolor } else { sit };
}
Off:
When use_small_heuristics is set to Off, the granular width settings are functionally disabled and ignored. See the documentation for the respective width config options for specifics.
enum Lorem {
Ipsum,
Dolor(bool),
Sit {
amet: Consectetur,
adipiscing: Elit,
},
}
fn main() {
lorem("lorem", "ipsum", "dolor", "sit", "amet", "consectetur", "adipiscing");
let lorem = Lorem {
ipsum: dolor,
sit: amet,
};
let lorem = if ipsum {
dolor
} else {
sit
};
}
Max:
When use_small_heuristics is set to Max, then each granular width setting is set to the same value as max_width.
So if max_width is set to 200, then all the width settings are also set to 200.
fn_call_width=200attr_fn_like_width=200struct_lit_width=200struct_variant_width=200array_width=200chain_width=200single_line_if_else_max_width=200single_line_let_else_max_width=200
enum Lorem {
Ipsum,
Dolor(bool),
Sit { amet: Consectetur, adipiscing: Elit },
}
fn main() {
lorem("lorem", "ipsum", "dolor", "sit", "amet", "consectetur", "adipiscing");
let lorem = Lorem { ipsum: dolor, sit: amet };
let lorem = if ipsum { dolor } else { sit };
}
See also:
max_widthfn_call_widthattr_fn_like_widthstruct_lit_widthstruct_variant_widtharray_widthchain_widthsingle_line_if_else_max_widthsingle_line_let_else_max_width
Replace uses of the try! macro by the ? shorthand
Stable: Yes
false (default):
fn main() {
let lorem = ipsum.map(|dolor| dolor.sit())?;
let lorem = try!(ipsum.map(|dolor| dolor.sit()));
}
true:
fn main() {
let lorem = ipsum.map(|dolor| dolor.sit())?;
}
This option is deprecated and has been replaced by style_edition.
version = "One" is equivalent to style_edition = "(2015|2018|2021)" and
version = "Two" is equivalent to style_edition = "2024"
Stable: No (tracking issue: #3383)
Example
version = "Two"
Forces the where clause to be laid out on a single line.
Stable: No (tracking issue: #3359)
false (default):
impl<T> Lorem for T
where
Option<T>: Ipsum,
{
// body
}
true:
impl<T> Lorem for T
where Option<T>: Ipsum
{
// body
}
See also brace_style, control_brace_style.
Break comments to fit on the line
Note that no wrapping will happen if:
- The comment is the start of a markdown header doc comment
- A URL was found in the comment
Stable: No (tracking issue: #3347)
false (default):
// Lorem ipsum dolor sit amet, consectetur adipiscing elit,
// sed do eiusmod tempor incididunt ut labore et dolore
// magna aliqua. Ut enim ad minim veniam, quis nostrud
// exercitation ullamco laboris nisi ut aliquip ex ea
// commodo consequat.
// Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
// Information on the lorem ipsum can be found at the following url: https://en.wikipedia.org/wiki/Lorem_ipsum. Its text is: lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
/// # This doc comment is a very long header (it starts with a '#'). Had it not been a header it would have been wrapped. But because it is a header, it will not be. That is because wrapping a markdown header breaks it.
struct Foo {}
true:
// Lorem ipsum dolor sit amet, consectetur adipiscing elit,
// sed do eiusmod tempor incididunt ut labore et dolore
// magna aliqua. Ut enim ad minim veniam, quis nostrud
// exercitation ullamco laboris nisi ut aliquip ex ea
// commodo consequat.
// Lorem ipsum dolor sit amet, consectetur adipiscing elit,
// sed do eiusmod tempor incididunt ut labore et dolore
// magna aliqua. Ut enim ad minim veniam, quis nostrud
// exercitation ullamco laboris nisi ut aliquip ex ea
// commodo consequat.
// Information on the lorem ipsum can be found at the following url: https://en.wikipedia.org/wiki/Lorem_ipsum. Its text is: lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
/// # This doc comment is a very long header (it starts with a '#'). Had it not been a header it would have been wrapped. But because it is a header, it will not be. That is because wrapping a markdown header breaks it.
struct Foo {}