--
You received this message because you are subscribed to the Google Groups "cxx" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cxx+uns...@chromium.org.
To post to this group, send email to c...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CAMGbLiFVvx20mhN_ZMc22NTueLxJV%2B5WSLwYOL7V85ZDo6paaQ%40mail.gmail.com.
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAMGbLiFVvx20mhN_ZMc22NTueLxJV%2B5WSLwYOL7V85ZDo6paaQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CACuR13ch3M-JfRepcx_9zA05iKY0t3NdRNwYLABGMPyPSmRaoQ%40mail.gmail.com.
--
Hi,(bcc chromium-dev, blink-dev -- join us over at cxx@ if you want to participate in the discussion)as of last week, I think all our toolchains support C++14.
What's new in C++14? See http://chromium-cpp.appspot.com/#core-review-14 and http://chromium-cpp.appspot.com/#library-review-14 -- thanks to jbroman for helping with documenting this. It's a fairly small language extension, but some things look useful (std::make_unique could replace base::MakeUnique, the extended constexpr support can be handy in some limited circumstances like e.g. base/numerics, etc).However, the google style guide doesn't make any recommendations about C++14 yet. So we'd have to guess which recommendations google style will make about C++14, and if we guess wrong that'd be somewhat unfortunate.Do people have an opinion on what to do? Hold off on C++14 stuff completely? Only allow "obviously ok" things (e.g. make_unique, but maybe not generic lambdas and generalized constexpr)? Do our best at guessing and then clean up after the fact when we guess wrong?Nico
--
On Fri, Aug 4, 2017 at 11:39 AM, Nico Weber <tha...@chromium.org> wrote:Hi,(bcc chromium-dev, blink-dev -- join us over at cxx@ if you want to participate in the discussion)as of last week, I think all our toolchains support C++14.Sanity check: does this include MSVC, for which AIUI we want to keep support for a release or 2 in case we have to revert back to it?
--Antoine--What's new in C++14? See http://chromium-cpp.appspot.com/#core-review-14 and http://chromium-cpp.appspot.com/#library-review-14 -- thanks to jbroman for helping with documenting this. It's a fairly small language extension, but some things look useful (std::make_unique could replace base::MakeUnique, the extended constexpr support can be handy in some limited circumstances like e.g. base/numerics, etc).However, the google style guide doesn't make any recommendations about C++14 yet. So we'd have to guess which recommendations google style will make about C++14, and if we guess wrong that'd be somewhat unfortunate.Do people have an opinion on what to do? Hold off on C++14 stuff completely? Only allow "obviously ok" things (e.g. make_unique, but maybe not generic lambdas and generalized constexpr)? Do our best at guessing and then clean up after the fact when we guess wrong?Nico
You received this message because you are subscribed to the Google Groups "cxx" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cxx+uns...@chromium.org.
To post to this group, send email to c...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CAMGbLiFVvx20mhN_ZMc22NTueLxJV%2B5WSLwYOL7V85ZDo6paaQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "cxx" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cxx+uns...@chromium.org.
To post to this group, send email to c...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CAMeTaZfn47HUOzyPRPbdL876UZNSYFM8M3skefj_i4FZ_VEz_Q%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "cxx" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cxx+uns...@chromium.org.
To post to this group, send email to c...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/2f1151aa-2c31-496c-94e9-819636c867da%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/cxx/CACuR13cbBpy%3DR5fo2-a427kXp4dcUtpBzqAP2wuS2z%2B2UbBDNg%40mail.gmail.com.
This is almost too trivial to ask, but I would also like to see the two ranges overloads for std::mismatch, std::equal and std::is_permutation: http://www.open-std.org/JTC1/sc22/WG21/docs/papers/2013/n3671.htmlI'm mostly interested in std::equal, as this allows easy implementation of operator== for custom container types, but the overloads for mismatch and permutation should be added for consistency as well.Furthermore, the two ranges std::equal is already used in the code base: https://codesearch.chromium.org/chromium/src/base/containers/span.h?l=71