Refine report_fatal_error guidance after post-commit review
authorAlex Bradbury <asb@lowrisc.org>
Fri, 18 Aug 2017 06:45:34 +0000 (06:45 +0000)
committerAlex Bradbury <asb@lowrisc.org>
Fri, 18 Aug 2017 06:45:34 +0000 (06:45 +0000)
commitf698a29a513566be1ae7f67be2afd4574999c9c2
treea261014fc3593b46069fca096c305c95dfe3f5f5
parent7182440fbd11ce1c3602bafd8aaba2da765dc94b
Refine report_fatal_error guidance after post-commit review

Use text suggested by Justin Bogner in post-commit review of r311146
<http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20170814/479898.html>,
which makes it clear that report_fatal_error shouldn't be used when there is a
practicable alternative. Also make this clearer in CodingStandards.

llvm-svn: 311147
llvm/docs/CodingStandards.rst
llvm/docs/ProgrammersManual.rst