Change:
and document some attributes and macros, but give few examples. Also there are some attributes/macros missing. Attributes: [x] abi (already in ; see commit ) [x] allow () [x] bench (delegated to ) [x] cfg (delegated to ) [x] deny () [x] deriving () [x] doc (mentioned in commit ; delegated to ) [x] forbid () [x] inline: (delegated to ) [x] lang (handled by ; done; see comment ) [x] license (delegated to ) [x] link (delegated to ; see commit ) [x] linkargs (delegated to ; see commit ) [x] linkname (already in ; see commit ) [x] noimplicitprelude, see [x] nolink (delegated to ) [x] nomangle (see ) [x] nostd (see ) [x] path (done; see commit ) [ ] shouldfail (see ) [x] start [x] staticassert (see ) [x] test (delegated to ) [x] unsafedestructor [x] warn () Macros: [x] asm [x] assert [x] asserteq [x] cfg [ ] cold [x] concatidents [x] bytes [x] debug () [x] env [x] error () [x] file () [x] format () [x] include () [x] includebin () [x] includestr () [x] info () [x] line [x] log () [x] logsyntax [x] macrorules [x] modulepath [x] optionenv [x] proto (is gone?) [ ] quoteexpr [ ] quoteitem [ ] quotepat [ ] quotestmt [ ] quotetokens [ ] quotety [x] stringify () [x] warn ()
Nominating for the well-covered milestone.
accepted for well-covered milestone
(the list here is too long to cope with sensibly so I am trying to make reasonably categorized sub-bugs.)
has an example in ; I'm going to cross it out above (with a note for why it has been struck out).
Funny, the attribute appears in , but not in any of our code nor is it handled in any way by the compiler. Such meta-data is propagated into the generated crate, but the current manual also says that all attribute names are effectively reserved (because only rustc interprets attributes). Perhaps we should handle this by explicitly listing the attributes that do not and will not have a default interpretation via rustc (where would be one of several attributes on that list)?
Okay there are only a handful of remaining small attributes that have not been delegated to some sub-bug. They can probably be handled just by associating them with this bug directly, unless someone feels like creating a new "miscellaneous" sub-bug, or new sub-bugs for each of them.
(and of course I haven't done anything with the list of macros yet).
I've collected most attributes currently in use at .
Documentation is low-hanging fruit, but not a reason to block 1.0. Not 1.0; P-low.
Is it normal that the macros doc seem to have disappeared from the official documentation? E.g. searching for returns no match (without the bang it returns plenty of function called , none of which seems to fit), and adapting the old path to is a 404
it's just a bug:
This is all messed up now that we have the Guide and no Tutorial.
is related
On May 12, 2013, kud1ing passed buck on "license" attribute to Bug 7961. On Oct 24, 2013, catamorphism passed buck on Bug 7961 back to this bug. At least two library crates won't build due to "license" attributes now being an error. (Was 3, but "stainless" was fixed. Currently broken: "http" and one other crate.)
Checking off , , , , , , and attributes, because they have docs. checking off and attributes because they're gone. checking off and macros because they have docs checking off macro because it's gone.

Discussion:
* `concat!` : concatenates a comma-separated list of literals * `concat_idents!` : create a new identifier by concatenating the arguments <ins> The following attributes are used for quasiquoting in procedural macros: * `quote_expr!` * `quote_item!` * `quote_pat!` * `quote_stmt!` * `quote_tokens!` * `quote_ty!` </ins> # Crates and source files Rust is a *compiled* language. Its semantics obey a *phase distinction*

item](#language-items) for more details. - `test` - indicates that this function is a test function, to only be compiled in case of `--test`. <ins> - `should_fail` - indicates that this test function should panic, inverting the success condition. - `cold` - The function is unlikely to be executed, so optimize it (and calls to it) differently. </ins> ### Static-only attributes