Skip to content

Commit

Permalink
Clarify that new lints are are T-lang changes
Browse files Browse the repository at this point in the history
They therefore require an RFC.
  • Loading branch information
nikomatsakis committed Feb 11, 2016
1 parent ee281d7 commit cc1282c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
1 change: 1 addition & 0 deletions compiler_changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ submitted later if there is scope for large changes to the language RFC.

## Changes which need an RFC

* New lints (these fall under the lang team)
* Large refactorings or redesigns of the compiler
* Changing the API presented to syntax extensions or other compiler plugins in
non-trivial ways
Expand Down
4 changes: 3 additions & 1 deletion lang_changes.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# 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 sub-team will do an initial triage of new PRs within a week of
Expand Down

0 comments on commit cc1282c

Please sign in to comment.