From cc1282c9a6aa4909016e5d564b306388832f313f Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Wed, 10 Feb 2016 17:13:27 -0500 Subject: [PATCH] Clarify that new lints are are T-lang changes They therefore require an RFC. --- compiler_changes.md | 1 + lang_changes.md | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/compiler_changes.md b/compiler_changes.md index 751377430..4b9f8cdf1 100644 --- a/compiler_changes.md +++ b/compiler_changes.md @@ -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 diff --git a/lang_changes.md b/lang_changes.md index 7e7e6a732..bc09d9a41 100644 --- a/lang_changes.md +++ b/lang_changes.md @@ -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