Skip to content

Commit 1ab8c3c

Browse files
authored
Merge pull request #2630 from jonas-schievink/1558-links
Add RFC PR and tracking issue links to RFC 1558
2 parents 4140615 + 0b7b431 commit 1ab8c3c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

text/1558-closure-to-fn-coercion.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
- Feature Name: closure_to_fn_coercion
22
- Start Date: 2016-03-25
3-
- RFC PR: (leave this empty)
4-
- Rust Issue: (leave this empty)
3+
- RFC PR: [rust-lang/rfcs#1558](https://github.com/rust-lang/rfcs/pull/1558)
4+
- Rust Issue: [rust-lang/rust#39817](https://github.com/rust-lang/rust/issues/39817)
55

66
# Summary
77
[summary]: #summary
@@ -153,13 +153,13 @@ and by circumstance later need to capture a variable. The required change from `
153153
be a breaking change.
154154

155155
We do expect crate authors to measure their API's flexibility in other areas, however, as when
156-
determining whether to take `&self` or `&mut self`. Taking a similar situation to the above:
156+
determining whether to take `&self` or `&mut self`. Taking a similar situation to the above:
157157

158158
```rust
159159
fn func_specific<'a>(&'a self) -> impl Fn() -> u32 {
160160
move || return self.field
161161
}
162-
162+
163163
fn func_general<'a>(&'a mut self) -> impl FnMut() -> u32 {
164164
move || { self.field += 1; return self.field; }
165165
}

0 commit comments

Comments
 (0)