summaryrefslogtreecommitdiffstats
path: root/llvm/docs/ProgrammersManual.rst
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2016-10-25 23:08:32 +0000
committerLang Hames <lhames@gmail.com>2016-10-25 23:08:32 +0000
commit8009f61c3d875ca7734b2a0c101fe68d80d12cfc (patch)
tree8b4d7a88088a8aa2160f700038c6d7f8853b776b /llvm/docs/ProgrammersManual.rst
parent1e04e46c7a32ebbb4b3a90327d37d1c1a19f76a9 (diff)
downloadbcm5719-llvm-8009f61c3d875ca7734b2a0c101fe68d80d12cfc.tar.gz
bcm5719-llvm-8009f61c3d875ca7734b2a0c101fe68d80d12cfc.zip
[docs] Avoid repetition of 'considerable' in Error docs.
llvm-svn: 285141
Diffstat (limited to 'llvm/docs/ProgrammersManual.rst')
-rw-r--r--llvm/docs/ProgrammersManual.rst20
1 files changed, 10 insertions, 10 deletions
diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst
index 954872e5917..4608a9c15e4 100644
--- a/llvm/docs/ProgrammersManual.rst
+++ b/llvm/docs/ProgrammersManual.rst
@@ -738,16 +738,16 @@ Building fallible iterators and iterator ranges
The archive walking examples above retrieve archive members by index, however
this requires considerable boiler-plate for iteration and error checking. We can
-clean this up considerably by using ``Error`` with the "fallible iterator"
-pattern. The usual C++ iterator patterns do not allow for failure on increment,
-but we can incorporate support for it by having iterators hold an Error
-reference through which they can report failure. In this pattern, if an
-increment operation fails the failure is recorded via the Error reference and
-the iterator value is set to the end of the range in order to terminate the
-loop. This ensures that the dereference operation is safe anywhere that an
-ordinary iterator dereference would be safe (i.e. when the iterator is not equal
-to end). Where this pattern is followed (as in the ``llvm::object::Archive``
-class) the result is much cleaner iteration idiom:
+clean this up by using ``Error`` with the "fallible iterator" pattern. The usual
+C++ iterator patterns do not allow for failure on increment, but we can
+incorporate support for it by having iterators hold an Error reference through
+which they can report failure. In this pattern, if an increment operation fails
+the failure is recorded via the Error reference and the iterator value is set to
+the end of the range in order to terminate the loop. This ensures that the
+dereference operation is safe anywhere that an ordinary iterator dereference
+would be safe (i.e. when the iterator is not equal to end). Where this pattern
+is followed (as in the ``llvm::object::Archive`` class) the result is much
+cleaner iteration idiom:
.. code-block:: c++
OpenPOWER on IntegriCloud