Displaying 2 results from an estimated 2 matches for "e2ac5f9".
Did you mean:
e2ac5f9e
2016 Dec 29
0
[cfe-dev] Modernizing LLVM Coding Style Guide and enforcing Clang-tidy
...every other case I would rather see push_back (and if an explicit
constructor call is necessary, an explicit constructor call).
My two cents.
-Chandler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161229/e2ac5f9e/attachment.html>
2016 Dec 29
2
[cfe-dev] Modernizing LLVM Coding Style Guide and enforcing Clang-tidy
Somewhat unfortunately, we have two discussions here:
- Clang-tidy has checks that might improve code -- should we deploy them?
If so which?
I'll address this in a separate email, and focus this one on:
- Should we have coding standards around 'push_back' and 'emplace_back',
and if so, what should they say?
I think the amount of confusion makes a coding standard useful.
As