From f6385a5d48fb5f17cf7c8d0426a75ab7112a8402 Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Tue, 10 Jul 2012 05:03:05 +0000
Subject: [PATCH] Jordan points out that this was incorrect: clang should
 recover from *errors* with fixits on them by following the recovery advised
 by the fixit, but if it is a fixit on a warning, then obviously the AST
 should be for the code as-written.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@159980 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/InternalsManual.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/InternalsManual.html b/docs/InternalsManual.html
index 6a673689168..38cd8498e66 100644
--- a/docs/InternalsManual.html
+++ b/docs/InternalsManual.html
@@ -453,8 +453,7 @@ the user the ability to automatically fix the problem.</p>
 <li>Since they are automatically applied if <code>-Xclang -fixit</code>
 is passed to the driver, they should only be used when it's very likely they
 match the user's intent.</li>
-<li>Clang must recover from the error or warning as if the fix-it had been
-applied.</li>
+<li>Clang must recover from errors as if the fix-it had been applied.</li>
 </ul>
 
 <p>If a fix-it can't obey these rules, put the fix-it on a note. Fix-its on
-- 
GitLab