[llvm-dev] RFC: changing variable naming rules in LLVM codebase
Renato Golin via llvm-dev
llvm-dev at lists.llvm.org
Tue Apr 30 11:20:23 PDT 2019
Wow, nice! Got here a bit late, but I'm happy we're finally taking this leap. :)
I agree with lower case variable names, but don't mind much between
camel and underscores. I personally use both depending on the phase of
the moon, so...
I really dislike variable type separation, especially in a
quasi-strongly typed language where we normally declare the casts
Using auto should be done when the variable is transient or the type
is too complex, which would provide complex and confusing mangling for
I like the separation of "useful acronyms" and "unnecessary
one-letters" and I think your document has a lot of common sense.
Some may say we'll shortly incur into a battle of styles, but I think
that won't last long. Our community is stable enough for that kind of
petty behaviour to endure. :)
I agree with Chris to change what's needed, not a huge refactor. This
has a good number of precedents in LLVM and reduces the impact of
non-functional changes to a minimum. This is also more ameanable to
Though, Rui's idea to do a bigger refactory in lld is brilliant, even
if a little stressfull. Again, we have precedent for big localised
changes and it mostly ends up as being good community work.
Thanks for pushing this, I agree the code ends up a bit dense, even in
places I am very familiar in, but haven't looked for a year, new
acronyms can make it hard to read. And if that increases the number of
new contributors, all the better!
On Tue, 12 Mar 2019 at 13:31, Michael Platings via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Thanks very much for all the feedback. I’ve tried to collect the information into a proposal for a transition plan: https://reviews.llvm.org/D59251.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev