bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Macros can now also be stmts and items.

Browse source
This commit is contained in:
Paul Stansifer 2012-11-22 11:54:52 -05:00 • committed by Graydon Hoare
parent f6a8ffc625
commit a88f9ac732
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/rust.md
View file

@ -494,7 +494,7 @@ transcriber : '(' transcriber * ')' | '[' transcriber * ']'
User-defined syntax extensions are called "macros", and they can be defined User-defined syntax extensions are called "macros", and they can be defined
with the `macro_rules!` syntax extension. User-defined macros can currently with the `macro_rules!` syntax extension. User-defined macros can currently
only be invoked in expression position. be invoked as expressions, statements, or items.
(A `sep_token` is any token other than `*` and `+`. A `non_special_token` is (A `sep_token` is any token other than `*` and `+`. A `non_special_token` is
any token other than a delimiter or `$`.) any token other than a delimiter or `$`.)
@ -510,7 +510,7 @@ For parsing reasons, delimiters must be balanced, but they are otherwise not spe
In the matcher, `$` _name_ `:` _designator_ matches the nonterminal in the In the matcher, `$` _name_ `:` _designator_ matches the nonterminal in the
Rust syntax named by _designator_. Valid designators are `item`, `block`, Rust syntax named by _designator_. Valid designators are `item`, `block`,
`stmt`, `pat`, `expr`, `ty` (type), `ident`, `path`, `matchers` (lhs of the `=>` in macro rules), `stmt`, `pat`, `expr`, `ty` (type), `ident`, `path`, `matchers` (lhs of the `=>` in macro rules),
`tt` (rhs of the `=>` in macro rules). In the transcriber, the designator is already known, and so only `tt` (rhs of the `=>` in macro rules). In the transcriber, the designator is already known, and so only
the name of a matched nonterminal comes after the dollar sign. the name of a matched nonterminal comes after the dollar sign.
@ -2196,7 +2196,7 @@ Records and structures can also be pattern-matched and their fields bound to var
When matching fields of a record, When matching fields of a record,
the fields being matched are specified first, the fields being matched are specified first,
then a placeholder (`_`) represents the remaining fields. then a placeholder (`_`) represents the remaining fields.
~~~~ ~~~~
# type options = {choose: bool, size: ~str}; # type options = {choose: bool, size: ~str};
# type player = {player: ~str, stats: (), options: options}; # type player = {player: ~str, stats: (), options: options};
@ -2726,7 +2726,7 @@ The kinds are:
structural types containing only other sendable types. structural types containing only other sendable types.
`Owned` `Owned`
: Types of this kind do not contain any borrowed pointers; : Types of this kind do not contain any borrowed pointers;
this can be a useful guarantee for code that breaks borrowing assumptions using [`unsafe` operations](#unsafe-functions). this can be a useful guarantee for code that breaks borrowing assumptions using [`unsafe` operations](#unsafe-functions).
`Copy` `Copy`
: This kind includes all types that can be copied. All types with : This kind includes all types that can be copied. All types with
sendable kind are copyable, as are managed boxes, managed closures, sendable kind are copyable, as are managed boxes, managed closures,