Remove the suggestion to not duplicate comments in header and

implementation files.  While doc generation systems don't need this,
humans do benefit from it.  Not everyone reads all code through doxygen.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@189704 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/CodingStandards.rst b/docs/CodingStandards.rst
index 9418680edc74a14a9cc39423b37eb70ade0051ea..3bf62514a9db3ba644b9b8cf44e867a55a7291fa 100644 (file)
--- a/docs/CodingStandards.rst
+++ b/docs/CodingStandards.rst
@@ -195,13 +195,6 @@ A documentation comment that uses all Doxygen features in a preferred way:
   /// \returns true on success.
   bool fooBar(bool Baz, StringRef Quux, std::vector<int> &Result);
 
-Don't duplicate the documentation comment in the header file and in the
-implementation file.  Put the documentation comments for public APIs into the
-header file.  Documentation comments for private APIs can go to the
-implementation file.  In any case, implementation files can include additional
-comments (not necessarily in Doxygen markup) to explain implementation details
-as needed.
-
 Don't duplicate function or class name at the beginning of the comment.
 For humans it is obvious which function or class is being documented;
 automatic documentation processing tools are smart enough to bind the comment