Skip to content

Commit

Permalink
Edition notes about
Browse files Browse the repository at this point in the history
  • Loading branch information
mark-i-m committed Sep 22, 2018
1 parent 3c181d2 commit c5eb0c9
Show file tree
Hide file tree
Showing 2 changed files with 39 additions and 0 deletions.
1 change: 1 addition & 0 deletions src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@
- [Macros](rust-2018/macros/index.md)
- [Custom Derive](rust-2018/macros/custom-derive.md)
- [Macro changes](rust-2018/macros/macro-changes.md)
- [At most one repetition](rust-2018/macros/at-most-once.md)
- [The compiler](rust-2018/the-compiler/index.md)
- [Improved error messages](rust-2018/the-compiler/improved-error-messages.md)
- [Incremental Compilation for faster compiles](rust-2018/the-compiler/incremental-compilation-for-faster-compiles.md)
Expand Down
38 changes: 38 additions & 0 deletions src/rust-2018/macros/at-most-once.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# At most one repetition

In Rust 2018, we have made a couple of changes to the macros-by-example syntax.

1. We have added a new Kleene operator `?` which means "at most one"
repetition. This operator does not accept a separator token.
2. We have disallowed using `?` as a separator to remove ambiguity with `?`.

For example, consider the following Rust 2015 code:

```rust
macro_rules! foo {
($a:ident, $b:expr) => {
println!("{}", $a);
println!("{}", $b);
}
($a:ident) => {
println!("{}", $a);
}
}
```

Macro `foo` can be called with 1 or 2 arguments; the second one is optional,
but you need a whole other matcher to represent this possibility. This is
annoying if your matchers are long. In Rust 2018, one can simply write the
following:

```rust
macro_rules! foo {
($a:ident $(, $b:expr)?) => {
println!("{}", $a);

$(
println!("{}", $b);
)?
}
}
```

0 comments on commit c5eb0c9

Please sign in to comment.