From fa57012d9d697ba237fbabf720e1813165c93682 Mon Sep 17 00:00:00 2001 From: Scott Olson Date: Tue, 6 Sep 2016 04:12:05 -0500 Subject: [PATCH] Block quote the entire style guideline example. Fixes my mistake from #1741. This also renders more obviously as a separate quotation. r? @eddyb --- text/1607-style-rfcs.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/text/1607-style-rfcs.md b/text/1607-style-rfcs.md index deefc3caf4f..162a580ce09 100644 --- a/text/1607-style-rfcs.md +++ b/text/1607-style-rfcs.md @@ -192,7 +192,9 @@ Guidelines may include more than one acceptable rule, but should offer guidance for when to use each rule (which should be formal enough to be used by a tool). -For example: "a struct literal must be formatted either on a single line (with +For example: + +> A struct literal must be formatted either on a single line (with spaces after the opening brace and before the closing brace, and with fields separated by commas and spaces), or on multiple lines (with one field per line and newlines after the opening brace and before the closing brace). The former @@ -200,7 +202,7 @@ approach should be used for short struct literals, the latter for longer struct literals. For tools, the first approach should be used when the width of the fields (excluding commas and braces) is 16 characters. E.g., -``` +> ```rust let x = Foo { a: 42, b: 34 }; let y = Foo { a: 42,