[www] r355447 - GSoC 2019 Static Analyzer project: Minor fixes suggested by Devin.

Artem Dergachev via llvm-commits llvm-commits at lists.llvm.org
Tue Mar 5 13:36:44 PST 2019


Author: dergachev
Date: Tue Mar  5 13:36:44 2019
New Revision: 355447

URL: http://llvm.org/viewvc/llvm-project?rev=355447&view=rev
Log:
GSoC 2019 Static Analyzer project: Minor fixes suggested by Devin.

Modified:
    www/trunk/OpenProjects.html

Modified: www/trunk/OpenProjects.html
URL: http://llvm.org/viewvc/llvm-project/www/trunk/OpenProjects.html?rev=355447&r1=355446&r2=355447&view=diff
==============================================================================
--- www/trunk/OpenProjects.html (original)
+++ www/trunk/OpenProjects.html Tue Mar  5 13:36:44 2019
@@ -295,28 +295,28 @@ main <a href="https://developers.google.
 
 <div class="www_text">
   <p><b>Description of the project:</b>
-	The idea is to improve the Clang Static Analyzer so that it becomes useful
-	for developers that work on Clang and LLVM themselves, as well as on other
+	The idea is to improve the Clang Static Analyzer so that it is useful
+	for developers who work on Clang and LLVM themselves, as well as on other
   LLVM-based projects, like Swift. LLVM makes use of C++ language features that
   the Static Analyzer has not yet been taught to understand. The analyzer also
   has false positives on some C++ idioms commonly used in the LLVM codebase.
   </p>
   <p>
 	The Static Analyzer is already useful for a variety of projects, but in order
-  to reach the "use your own tools" checkpoint, we'd have to classify, debug,
+  to reach the "use your own tools" checkpoint, we'll have to classify, debug,
   and, ideally, eliminate the most common sources of false positives
   on our code. It would be the best to fix false positives by improving
   the Static Analyzer itself, but it may also sometimes be feasible to add
   a few suppressions (such as assertions) within the LLVM source code so that
   it is easier for both humans and the Analyzer to understand what's going on.
-  And, of course, it's great to report and maybe even fix the true positives
-  that we manage to find!
+  And, of course, it would be great to report and maybe even fix the true
+  positives that we manage to find!
   </p>
 
   <p><b>Expected results:</b>
   Results produced by the Analyzer on LLVM itself should become more or
   less correct: warnings are useful, false alarms are gone. This lets
-  more and more LLVM developers adopt the Static Analyzer in their daily lifes
+  more and more LLVM developers adopt the Static Analyzer in their daily lives
   or CI workflows.
   </p>
 




More information about the llvm-commits mailing list