dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix link in RFC template and stuff

This commit is contained in:
Mazdak Farrokhzad 2018-07-17 02:36:36 +02:00 committed by GitHub
parent 2a0a320df7
commit cc2faf7c4d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
0000-template.md
View File

@ -43,7 +43,7 @@ The section should return to the examples given in the previous section, and exp
Why should we *not* do this?
# Rationale and alternatives
[alternatives]: #alternatives
[rationale-and-alternatives]: #rationale-and-alternatives
- Why is this design the best in the space of possible designs?
- What other designs have been considered and what is the rationale for not choosing them?
@ -67,7 +67,7 @@ Note that while precedent set by other languages is some motivation, it does not
Please also take into consideration that rust sometimes intentionally diverges from common language features.
# Unresolved questions
[unresolved]: #unresolved-questions
[unresolved-questions]: #unresolved-questions
- What parts of the design do you expect to resolve through the RFC process before this gets merged?
- What parts of the design do you expect to resolve through the implementation of this feature before stabilization?