diff options
author | Dmitri Gribenko <gribozavr@gmail.com> | 2012-09-18 14:00:58 +0000 |
---|---|---|
committer | Dmitri Gribenko <gribozavr@gmail.com> | 2012-09-18 14:00:58 +0000 |
commit | be88f563bf6c7640ab1f74472d730e0fe71061b2 (patch) | |
tree | 082e1d3390ec861f7f24be96ab532db0ba24e718 | |
parent | 1b5585a35092726abac4ef9358fb9b30ac1b3e6b (diff) | |
download | bcm5719-llvm-be88f563bf6c7640ab1f74472d730e0fe71061b2.tar.gz bcm5719-llvm-be88f563bf6c7640ab1f74472d730e0fe71061b2.zip |
Coding standards: fix typo: '= deleted' -> '= delete'.
llvm-svn: 164126
-rw-r--r-- | llvm/docs/CodingStandards.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/CodingStandards.rst b/llvm/docs/CodingStandards.rst index bc58f57cb74..4d16e2a9bd6 100644 --- a/llvm/docs/CodingStandards.rst +++ b/llvm/docs/CodingStandards.rst @@ -826,14 +826,14 @@ unimplemented copy constructor and copy assignment operator and make them 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++ |