While at it, added a dump method to RangeSet.
Details
Diff Detail
- Repository
- rC Clang
Event Timeline
After thinking about this change a bit longer, I think it does not make sense.
Albeit poorly named, the previous design had a purpose: RangedConstraintManager is a public interface, and RangeConstraintManager is a private implementation.
Exposing both in the header does not make sense.
For exposing the factory could you just move the factory and it's getter?
Another solution is just merging the two classes entirely, but that's more heavyweight, and would force exposing private functions in a header (but those could be just moved to static C functions).
@NoQ further comments?
include/clang/StaticAnalyzer/Core/PathSensitive/RangedConstraintManager.h | ||
---|---|---|
120 | Adding this dump method resulted in a bot breakage on our side (during the linking process). |
Since we decided to go with the other approach in D48565, we don't actually need this patch anymore.
Adding this dump method resulted in a bot breakage on our side (during the linking process).
I'm not 100% sure why, but since this belongs in a separate review anyway, could we drop those lines?