Previously, CallDescription simply referred to the qualified name parts
by const char* pointers.
In the future, we might want to dynamically load and populate
CallDescriptionMaps, hence we will need the CallDescriptions to
actually own their qualified name parts.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Why though? Are you actually putting anything in there that isn't a static string literal?
Comment Actions
If we plan in the future to dynamically populate CallDescriptionMaps then we will need owning semantics for CallDescriptions actually owning the qualified name parts.
Consider the GenericTaintChecker, which currently implements an ad-hoc function call matching just because of this.
Ideally, what we want is just parsing the config and populating the corresponding maps.
On the other hand, it could come in handy in the StdLibraryChecker as well, if we decide to hoist the DSL and let users specify their API in config files in a similar manner.