Paul =?utf-8?q?Heidekrüger?= <paul.heidekrue...@tum.de>,
Paul =?utf-8?q?Heidekrüger?= <paul.heidekrue...@tum.de>,
Paul =?utf-8?q?Heidekrüger?= <paul.heidekrue...@tum.de>,
Paul =?utf-8?q?Heidekrüger?= <paul.heidekrue...@tum.de>,
Paul =?utf-8?q?Heidekrüger?= <paul.heidekrue...@tum.de>
Message-ID:
In-Reply-To: <llvm.org/llvm/llvm-project/pull/95...@github.com>


leunam99 wrote:

> I still think "AvoidBoundErrors" is the best name since it maps exactly to 
> what the guidelines call it.

For me, this sounds to general for what the check currently does. The 
Enforcement section at the end of the rule SL.con.3 states:
> Issue a diagnostic for any call to a standard-library function that is not 
> bounds-checked.

The guidelines do not provide a list of such functions and we are not familliar 
enough with the standard library to create a comprehensive list ourself, so at 
this time, we are unable to implement the full rule.


https://github.com/llvm/llvm-project/pull/95220
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to