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

I always find myself adding these anchors (or some variant thereof) 

while I'm drafting an RFC.

Lets put them into the template so that people will get them by
default.

(Hopefully we don't need an RFC to decide whether to change the RFC
template in this manner.)
This commit is contained in:
Felix S. Klock II 2015-10-20 16:45:27 +02:00
parent b8da6c79a6
commit 67c2049be5
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
0000-template.md
View File

@ -4,27 +4,33 @@
- Rust Issue: (leave this empty)
# Summary
[summary]: #summary
One para explanation of the feature.
# Motivation
[motivation]: #motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
# Detailed design
[design]: #detailed-design
This is the bulk of the RFC. Explain the design in enough detail for somebody familiar
with the language to understand, and for somebody familiar with the compiler to implement.
This should get into specifics and corner-cases, and include examples of how the feature is used.
# Drawbacks
[drawbacks]: #drawbacks
Why should we *not* do this?
# Alternatives
[alternatives]: #alternatives
What other designs have been considered? What is the impact of not doing this?
# Unresolved questions
[unresolved]: #unresolved-questions
What parts of the design are still TBD?