* Use spaces around binary operators, including the equals sign in attributes:
-``` rust
+```rust,ignore
#[deprecated = "Use `bar` instead."]
fn foo(a: usize, b: usize) -> usize {
a + b
* Use a space after colons and commas:
-``` rust
+```rust,ignore
fn foo(a: Bar);
MyStruct { foo: 3, bar: 4 }
* Use a space after the opening and before the closing brace for
single line blocks or `struct` expressions:
-``` rust
+```rust,ignore
spawn(proc() { do_something(); })
Point { x: 0.1, y: 0.3 }
* For multiline function signatures, each new line should align with the
first parameter. Multiple parameters per line are permitted:
-``` rust
+```rust,ignore
fn frobnicate(a: Bar, b: Bar,
c: Bar, d: Bar)
-> Bar {
signatures. However, if the final argument begins a new block, the
contents of the block may begin on a new line, indented one level:
-``` rust
+```rust,ignore
fn foo_bar(a: Bar, b: Bar,
c: |Bar|) -> Bar {
...
> **[FIXME]** Do we also want to allow the following?
>
-> ```rust
+> ```rust,ignore
> frobnicate(
> arg1,
> arg2,
> * **[Deprecated]** If you have multiple patterns in a single `match`
> arm, write each pattern on a separate line:
>
-> ``` rust
+> ```rust,ignore
> match foo {
> bar(_)
> | baz => quux,
to provide alignment.
-``` rust
+```rust,ignore
// Good
struct Foo {
short: f64,