Skip to content

Commit 310e722

Browse files
authored
RFC 2300
1 parent 9ee10b4 commit 310e722

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

text/0000-self-in-typedefs.md renamed to text/2300-self-in-typedefs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
- Feature Name: self_in_typedefs
1+
- Feature Name: `self_in_typedefs`
22
- Start Date: 2018-01-17
3-
- RFC PR: (leave this empty)
4-
- Rust Issue: (leave this empty)
3+
- RFC PR: [rust-lang/rfcs#2300](https://github.com/rust-lang/rfcs/pull/2300)
4+
- Rust Issue: [rust-lang/rust#49303](https://github.com/rust-lang/rust/issues/49303)
55

66
# Summary
77
[summary]: #summary
@@ -726,4 +726,4 @@ is preferred.
726726
within impls (for example, as the value for an associated type). Do we ever want
727727
to support that, and if so, how should we resolve the ambiguity? **A** possible,
728728
interpretation and way to solve the ambiguity consistently is discussed in the
729-
rationale.
729+
rationale.

0 commit comments

Comments
 (0)