Lift up FIXMEs

Author: aturon

style/braces.md

@@ -1,6 +1,6 @@
-% Braces, semicolons, and commas
+% Braces, semicolons, and commas [FIXME: needs RFC]
 
-### Opening braces always go on the same line. [FIXME: needs RFC]
+### Opening braces always go on the same line.
 
 ``` rust
 fn foo() {
@@ -28,7 +28,7 @@ frob(|x| {
 })
 ```
 
-### `match` arms get braces, except for single-line expressions. [FIXME: needs RFC]
+### `match` arms get braces, except for single-line expressions.
 
 ``` rust
 match foo {
@@ -40,7 +40,7 @@ match foo {
 }
 ```
 
-### `return` statements get semicolons. [FIXME: needs RFC]
+### `return` statements get semicolons.
 
 ``` rust
 fn foo() {
@@ -54,7 +54,7 @@ fn foo() {
 }
 ```
 
-### Trailing commas [FIXME: needs RFC]
+### Trailing commas
 
 > **[FIXME]** We should have a guideline for when to include trailing
 > commas in `struct`s, `match`es, function calls, etc.

style/features.md

@@ -1,4 +1,4 @@
-## `return`
+## `return` [FIXME: needs RFC]
 
 Terminate `return` statements with semicolons:
 

style/imports.md

@@ -1,4 +1,4 @@
-% Imports
+% Imports [FIXME: needs RFC]
 
 The imports of a crate/module should consist of the following
 sections, in order, with a blank space between each:
@@ -26,7 +26,7 @@ use mylib::webserver;
 pub use self::types::Webdata;
 ```
 
-### Avoid `use *`, except in tests. [FIXME: needs RFC]
+### Avoid `use *`, except in tests.
 
 Glob imports have several downsides:
 * They make it harder to tell where names are bound.
@@ -36,7 +36,7 @@ Glob imports have several downsides:
 When writing a [`test` submodule](../testing/README.md), importing `super::*` is appropriate
 as a convenience.
 
-### Prefer fully importing types/traits while module-qualifying functions. [FIXME: needs RFC]
+### Prefer fully importing types/traits while module-qualifying functions.
 
 For example:
 

style/organization.md

@@ -1,13 +1,13 @@
-% Organization
+% Organization [FIXME: needs RFC]
 
 > **[FIXME]** What else?
 
-### Reexport the most important types at the crate level. [FIXME: needs RFC]
+### Reexport the most important types at the crate level.
 
 Crates `pub use` the most common types for convenience, so that clients do not
 have to remember or write the crate's module hierarchy to use these types.
 
-### Define types and operations together. [FIXME: needs RFC]
+### Define types and operations together.
 
 Type definitions and the functions/methods that operate on them should be
 defined together in a single module, with the type appearing above the