]> granicus.if.org Git - clang/commit
Clarify when fix-it hints on warnings are appropriate
authorAaron Puchert <aaron.puchert@sap.com>
Fri, 31 May 2019 21:27:39 +0000 (21:27 +0000)
committerAaron Puchert <aaron.puchert@sap.com>
Fri, 31 May 2019 21:27:39 +0000 (21:27 +0000)
commit83b6db970ca7d26ee646a0d7a2087941280b936f
tree0a0f576ed589d18e6e60473cccc4a0f6a4515990
parenta5d3721dd8cb849e7eec7c13881d28257203b9d7
Clarify when fix-it hints on warnings are appropriate

Summary:
This is not a change in the rules, it's meant as a clarification about
warnings. Since the recovery from warnings is a no-op, the fix-it hints
on warnings shouldn't change anything. Anything that doesn't just
suppress the warning and changes the meaning of the code (even if it's
for the better) should be on an additional note.

Reviewers: rsmith, aaron.ballman

Reviewed By: aaron.ballman

Subscribers: cfe-commits, thakis

Tags: #clang

Differential Revision: https://reviews.llvm.org/D62470

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@362266 91177308-0d34-0410-b5e6-96231b3b80d8
docs/InternalsManual.rst