Remove enforcement rules of rule F.17 about cppcoreguidelines HOT 7 OPEN

In this case, the two rules are addressing different aspects. F rules are specifically about functions while Con rules are specifically about constants. The two compliment each other - with Con.3 being the general case and F.17 being a specific case of Con.3 within the function context.

from cppcoreguidelines.

Thanks for your answer Benjamen. As far as I can determine, F.17 is a full subset of Con.3. So every time F.17 fires, Con.3 will fire as well. In such a situation, the question is what the added value is of F.17 and from a coding standard point of view, F.17 should be removed. If F.17 is not a full subset of some other rule, it is important to extract its unique part and remove the overlap.

Is this something that can be done?

These questions/this issue might sound a bit pedantic, but we are dealing with customers using our implementation of your C++ core guidelines (we are talking about 50,000+ software engineers) that don't understand why a situation is flagged twice by different rules and I think they are right.

from cppcoreguidelines.