[llvm-commits] [llvm] r164126 - /llvm/trunk/docs/CodingStandards.rst

Dmitri Gribenko gribozavr at gmail.com
Tue Sep 18 07:00:58 PDT 2012


Author: gribozavr
Date: Tue Sep 18 09:00:58 2012
New Revision: 164126

URL: http://llvm.org/viewvc/llvm-project?rev=164126&view=rev
Log:
Coding standards: fix typo: '= deleted' -> '= delete'.

Modified:
    llvm/trunk/docs/CodingStandards.rst

Modified: llvm/trunk/docs/CodingStandards.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/CodingStandards.rst?rev=164126&r1=164125&r2=164126&view=diff
==============================================================================
--- llvm/trunk/docs/CodingStandards.rst (original)
+++ llvm/trunk/docs/CodingStandards.rst Tue Sep 18 09:00:58 2012
@@ -826,14 +826,14 @@
 private. This would give a compiler error for accessing a private method or a
 linker error because it wasn't implemented.
 
-With C++11, we can mark methods that won't be implemented with ``= deleted``.
+With C++11, we can mark methods that won't be implemented with ``= delete``.
 This will trigger a much better error message and tell the compiler that the
 method will never be implemented. This enables other checks like
 ``-Wunused-private-field`` to run correctly on classes that contain these
 methods.
 
 To maintain compatibility with C++03, ``LLVM_DELETED_FUNCTION`` should be used
-which will expand to ``= deleted`` if the compiler supports it. These methods
+which will expand to ``= delete`` if the compiler supports it. These methods
 should still be declared private. Example of the uncopyable pattern:
 
 .. code-block:: c++





More information about the llvm-commits mailing list