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

Address different kinds of unresolved questions

This commit is contained in:
Carol (Nichols || Goulding) 2017-07-19 16:25:48 -04:00
parent 4a3f5c5570
commit 117f9b96f8
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
0000-template.md
View File

@ -52,4 +52,6 @@ Why should we *not* do this?
# Unresolved questions
[unresolved]: #unresolved-questions
What parts of the design are still TBD?
- 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?
- What related issues do you consider out of scope for this RFC tha could be addressed in the future independently of the solution that comes out of this RFC?