search for: d57896

Displaying 6 results from an estimated 6 matches for "d57896".

Did you mean: d37896
2019 Feb 07
9
RFC: changing variable naming rules in LLVM codebase
...seemed to be general agreement that the status quo is not ideal. Chris Lattner pointed out that this came up in 2014 as well: http://lists.llvm.org/pipermail/llvm-dev/2014-October/077685.html I've created a patch to implement the change. Review and comments welcome: https://reviews.llvm.org/D57896 <http://lists.llvm.org/pipermail/llvm-dev/2014-October/077685.html> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190207/bd7df9f6/attachment.html>
2019 Apr 25
2
Coding style. VariableNames, not variableNames?
Hey, A colleague just pointed out that the style guide says: *Variable names* ... should be camel case, and start with an upper case letter I was under the impression that variables were supposed to be camel case, without a leading upper case, as currently recommended for function names. Is this a somewhat recent change? If so, could someone share a regex / script for updating the previous style
2019 Feb 12
2
changing variable naming rules in LLVM codebase
...us quo is not ideal. > > > > Chris Lattner pointed out that this came up in 2014 as well: http://lists.llvm.org/pipermail/llvm-dev/2014-October/077685.html > > > > I've created a patch to implement the change. Review and comments welcome: https://reviews.llvm.org/D57896 > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
2019 Feb 12
2
changing variable naming rules in LLVM codebase
...;> >>> Chris Lattner pointed out that this came up in 2014 as well: http://lists.llvm.org/pipermail/llvm-dev/2014-October/077685.html>> >>> >>> >>> I've created a patch to implement the change. Review and comments welcome: https://reviews.llvm.org/D57896>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> llvm-dev at lists.llvm.org >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev> >> _______________________________________________ >> LLVM Dev...
2019 Feb 18
4
RFC: changing variable naming rules in LLVM codebase
On 2/18/2019 4:15 AM, Michael Platings via llvm-dev wrote: > Taking my previous example [1]: > > InnerLoopVectorizer LB(L, PSE, LI, DT, TLI, TTI, AC, ORE, VF.Width, IC, > &LVL, &CM); > > If we imagine that over time it evolves such that 50% of the variables have been renamed to camelBack versions of the type names, then it will look like this: > >
2019 Feb 13
4
changing variable naming rules in LLVM codebase
...ut that this came up in 2014 as well: >> http://lists.llvm.org/pipermail/llvm-dev/2014-October/077685.html>> >> >>> >> >>> >> >>> I've created a patch to implement the change. Review and comments >> welcome: https://reviews.llvm.org/D57896>> >> >>> _______________________________________________ >> >>> LLVM Developers mailing list >> >>> llvm-dev at lists.llvm.org >> >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev> >> >> ____________________...