diff options
| author | Nathan Lanza <nathan@lanza.io> | 2019-07-18 05:24:22 +0000 |
|---|---|---|
| committer | Nathan Lanza <nathan@lanza.io> | 2019-07-18 05:24:22 +0000 |
| commit | 4f93b8b56f5982d19b8b55b8c575887c17e15588 (patch) | |
| tree | 9712deb31f2f2649b2141b6049afce04fdf7e1b5 /llvm/docs/ProgrammersManual.rst | |
| parent | 44deaf7e54ef55a55965f0c5cf41d4436120f75f (diff) | |
Fix typo in programmer's manual cantFile -> cantFail
llvm-svn: 366403
Diffstat (limited to 'llvm/docs/ProgrammersManual.rst')
| -rw-r--r-- | llvm/docs/ProgrammersManual.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst index b6d751d7cbe9..a96f8b4b714c 100644 --- a/llvm/docs/ProgrammersManual.rst +++ b/llvm/docs/ProgrammersManual.rst @@ -821,7 +821,7 @@ T value: Like the ExitOnError utility, cantFail simplifies control flow. Their treatment of error cases is very different however: Where ExitOnError is guaranteed to -terminate the program on an error input, cantFile simply asserts that the result +terminate the program on an error input, cantFail simply asserts that the result is success. In debug builds this will result in an assertion failure if an error is encountered. In release builds the behavior of cantFail for failure values is undefined. As such, care must be taken in the use of cantFail: clients must be |