forked from OSchip/llvm-project
5c6fc36de8
The idea behind this heuristic is that normally the visitor is there to inform the user that a certain function may fail to initialize a certain out-parameter. For system header functions this is usually dictated by the contract, and it's unlikely that the header function has accidentally forgot to put the value into the out-parameter; it's more likely that the user has intentionally skipped the error check. Warnings on skipped error checks are more like security warnings; they aren't necessarily useful for all users, and they should instead be introduced on a per-API basis. Differential Revision: https://reviews.llvm.org/D60107 llvm-svn: 357810 |
||
---|---|---|
.. | ||
Models | ||
expected-plists | ||
ctu-chain.cpp | ||
ctu-other.c | ||
ctu-other.c.externalDefMap.txt | ||
ctu-other.cpp | ||
ctu-other.cpp.externalDefMap.txt | ||
localization-pch.h | ||
no-store-suppression.h | ||
qt-simulator.h | ||
system-header-simulator-cxx-std-suppression.h | ||
system-header-simulator-cxx.h | ||
system-header-simulator-for-cxx-uninitialized-object.h | ||
system-header-simulator-for-malloc.h | ||
system-header-simulator-for-nullability-cxx.h | ||
system-header-simulator-for-nullability.h | ||
system-header-simulator-for-objc-dealloc.h | ||
system-header-simulator-for-pthread-lock.h | ||
system-header-simulator-for-simple-stream.h | ||
system-header-simulator-for-valist.h | ||
system-header-simulator-objc.h | ||
system-header-simulator.h |