rfc, prior-art: communicate intentional divergence per @wycats's comments

This commit is contained in:
Mazdak Farrokhzad 2018-02-15 06:28:46 +01:00
parent 1118f8872d
commit e225f1be3b
2 changed files with 4 additions and 2 deletions

View File

@ -64,6 +64,7 @@ This section is intended to encourage you as an author to think about the lesson
If there is no prior art, that is fine - your ideas are interesting to us whether they are brand new or if it is an adaptation from other languages.
Note that while precedent set by other languages is some motivation, it does not on its own motivate an RFC.
Please also take into consideration that rust sometimes intentionally diverges from common language features.
# Unresolved questions
[unresolved]: #unresolved-questions

View File

@ -111,8 +111,9 @@ text to the RFC template before the section *Unresolved questions*:
> interesting to us whether they are brand new or if it is an adaptation
> from other languages.
>
> Note that while precedent set by other languages is some motivation,
> it does not on its own motivate an RFC.
> Note that while precedent set by other languages is some motivation, it does
> not on its own motivate an RFC. Please also take into consideration that rust
> sometimes intentionally diverges from common language features.
# Drawbacks
[drawbacks]: #drawbacks