read from a file that might contain non-ASCII characters. The problem comes
up when the code uses the ``-1`` integer value as EOF, while the 255 character
code is also stored as ``-1`` in two's complement form of char type.
-See a simple example of this bellow. This code stops not only when it reaches
+See a simple example of this below. This code stops not only when it reaches
the end of the file, but also when it gets a character with the 255 code.
.. code-block:: c++
Lambdas
-------
-The check does not currently report unsafe optional acceses in lambdas.
+The check does not currently report unsafe optional accesses in lambdas.
A future version will expand the scope to lambdas, following the rules
outlined above. It is best to follow the same principles when using
optionals in lambdas.
Warns on unused function return values. Many of the standard library functions
return a value that indicates if the call was successful. Ignoring the returned
-value can cause unexpected behavior if an error has occured. The following
+value can cause unexpected behavior if an error has occurred. The following
functions are checked:
* aligned_alloc()
are not susceptible to slicing and the usage of string literals is
idiomatic.
* Catching character pointers (``char``, ``wchar_t``, unicode character types)
- will not be flagged to allow catching sting literals.
+ will not be flagged to allow catching string literals.
* Moved named values will not be flagged as not throwing an anonymous
temporary. In this case we can be sure that the user knows that the object
can't be accessed outside catch blocks handling the error.