Displaying 2 results from an estimated 2 matches for "ea62499f".
2019 Sep 06
3
[RFC] changing variable naming rules
...on't break anything.
5. Give a heads-up and submit a sweeping change to the entire LLVM.
I'd like to submit a sweeping change after LLVM migrates to GitHub to minimize confusion.
[1] http://lists.llvm.org/pipermail/llvm-dev/2019-February/130083.html
[2] https://protect2.fireeye.com/url?k=ea62499f-b6f04480-ea620904-0cc47ad93db4-ecd933b4f617d714&q=1&u=https%3A%2F%2Fgithub.com%2Fllvm%2Fllvm-project%2Ftree%2Fmaster%2Flld
[3] https://protect2.fireeye.com/url?k=3251f903-6ec3f41c-3251b998-0cc47ad93db4-9f9d4ccc78551a27&q=1&u=https%3A%2F%2Fgithub.com%2Fllvm%2Fllvm-project%2Fcommit%2F...
2019 Sep 04
7
[RFC] changing variable naming rules
Hi all,
To get wider visibility, build a broader consensus and address concerns on
this topic, I'm again raising this as an RFC. This is a proposal to change
the rule for variable names from CamelCase to camelBack _really this time_.
Background:
This has been proposed several times on this mailing list in the past. Most
recent one was by Michael Platings in February this year [1], and there