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

Clarify that new lints are are T-lang changes 

They therefore require an RFC.
This commit is contained in:
Niko Matsakis 2016-02-10 17:13:27 -05:00
parent ee281d7119
commit cc1282c9a6
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
compiler_changes.md
View File

@ -21,6 +21,7 @@ submitted later if there is scope for large changes to the language RFC.
## Changes which need an RFC ## Changes which need an RFC
* New lints (these fall under the lang team)
* Large refactorings or redesigns of the compiler * Large refactorings or redesigns of the compiler
* Changing the API presented to syntax extensions or other compiler plugins in * Changing the API presented to syntax extensions or other compiler plugins in
non-trivial ways non-trivial ways

4
lang_changes.md
View File

@ -1,6 +1,8 @@
# RFC policy - language design # RFC policy - language design
Pretty much every change to the language needs an RFC. Pretty much every change to the language needs an RFC. Note that new
lints (or major changes to an existing lint) are considered changes to
the language.
Language RFCs are managed by the language sub-team, and tagged `T-lang`. The Language RFCs are managed by the language sub-team, and tagged `T-lang`. The
language sub-team will do an initial triage of new PRs within a week of language sub-team will do an initial triage of new PRs within a week of