diff options
| author | Alexis Bourget <alexis.bourget@gmail.com> | 2020-06-23 11:42:15 +0200 |
|---|---|---|
| committer | Alexis Bourget <alexis.bourget@gmail.com> | 2020-06-23 11:42:15 +0200 |
| commit | 2853448426ce76926baa7e6e6173c15228e4951a (patch) | |
| tree | 2ec3c630e62841c3dc7a955821a5a858541c4875 /src | |
| parent | dcd470fe1be03136a8e1794b7e2cc6179bbd9d92 (diff) | |
| download | rust-2853448426ce76926baa7e6e6173c15228e4951a.tar.gz rust-2853448426ce76926baa7e6e6173c15228e4951a.zip | |
Document the ref keyword
Diffstat (limited to 'src')
| -rw-r--r-- | src/libstd/keyword_docs.rs | 44 |
1 files changed, 42 insertions, 2 deletions
diff --git a/src/libstd/keyword_docs.rs b/src/libstd/keyword_docs.rs index a4996d9eee8..aca7f880ecd 100644 --- a/src/libstd/keyword_docs.rs +++ b/src/libstd/keyword_docs.rs @@ -991,9 +991,49 @@ mod pub_keyword {} // /// Bind by reference during pattern matching. /// -/// The documentation for this keyword is [not yet complete]. Pull requests welcome! +/// `ref` annotates pattern bindings to make them borrow rather than move. +/// It is **not** a part of the pattern as far as matching is concerned. +/// +/// By default, [`match`] statements consume all they can, which can sometimes +/// be a problem, when you don't really need the value to be moved and owned: +/// +/// ```compile_fail,E0382 +/// let maybe_name = Some(String::from("Alice")); +/// // The variable 'maybe_name' is consumed here ... +/// match maybe_name { +/// Some(n) => println!("Hello, {}", n), +/// _ => println!("Hello, world"), +/// } +/// // ... and now unavailable. +/// println!("Hello again, {}", maybe_name.unwrap_or("world".into())); +/// ``` /// -/// [not yet complete]: https://github.com/rust-lang/rust/issues/34601 +/// Using the `ref` keyword, the value is only borrowed, not moved, making +/// available for use after the [`match`] statement: +/// +/// ``` +/// let maybe_name = Some(String::from("Alice")); +/// // Using `ref`, the value is borrowed, not moved ... +/// match maybe_name { +/// Some(ref n) => println!("Hello, {}", n), +/// _ => println!("Hello, world"), +/// } +/// // ... and it's available here ! +/// println!("Hello again, {}", maybe_name.unwrap_or("world".into())); +/// ``` +/// +/// # `&` vs `ref` +/// +/// - `&` denotes that your pattern expects a reference to an object. Hence `&` +/// is a part of said pattern: `&Foo` matches different objects than `Foo` does. +/// +/// - `ref` indicates that you want a reference to an unpacked value. It is not +/// matched against: `Foo(ref foo)` matches the same objects as `Foo(foo)`. +/// +/// See also the [Reference] for more information. +/// +/// [`match`]: keyword.match.html +/// [Reference]: ../reference/patterns.html#identifier-patterns mod ref_keyword {} #[doc(keyword = "return")] |
