(original) (raw)
On Oct 13, 2014, at 3:44 PM, Chandler Carruth <chandlerc@google.com> wrote:But I also really appreciate why most coding standards I have seen advocated try to use distinguished naming conventions for these things to make it easier to tell at a glance what things are what. And I suspect this kind of optimization for skimming and rapid comprehension is the correct way for LLVM to structure its style.
I agree.
My position is that trading one set of collisions for another set of collisions is a poor tradeoff. I would much rather trade for no collisions.
I purposefully did not discuss data member names in my RFC because as I found in the lld conventions discussions, that LLVM�ers seemed shocked by having different naming conventions for data members than local (stack) variables.
-Nick