<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello again WebKitten!<div class=""><br class=""></div><div class="">April 2018 is fast approaching, which means that we might be able to require GCC 6 and all the great C++17 features that’ll come with it. So what say you?</div><div class="">From C++17 it looks like we wouldn’t get quite a few things, but we’d be able to use a few nice things (see <a href="http://en.cppreference.com/w/cpp/compiler_support" class="">the table</a>).</div><div class=""><br class=""></div><div class="">JF</div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 4, 2017, at 16:00, Michael Catanzaro <<a href="mailto:mcatanzaro@igalia.com" class="">mcatanzaro@igalia.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Fri, Aug 4, 2017 at 3:48 PM, Yusuke SUZUKI <<a href="mailto:utatane.tea@gmail.com" class="">utatane.tea@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">Possibly, mcatanzaro and clopez know much about WebKitGTK+ compiler dependencies.<br class=""></blockquote><br class="">As a result of the C++14 discussion on this list a few months ago, we relaxed our dependencies policy [1] to allow upgrading to GCC 5 one year earlier than planned, to the displeasure of some of our distributors who now have to build a custom compiler as part of their WebKit builds. We would prefer not to relax the policy further.<br class=""><br class="">Our current schedule looks like:<br class=""><br class="">* GCC 6 could be required in April 2018 (next Ubuntu LTS release)<br class="">* GCC 7 (required for C++17) could be required likely late in 2019 (next Debian stable release)<br class=""><br class="">Is that acceptable for Apple?<br class=""><br class="">Michael<br class=""><br class="">[1] <a href="https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy" class="">https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy</a><br class=""></div></div></blockquote><br class=""></div></div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 4, 2017, at 13:39, JF Bastien <<a href="mailto:jfbastien@apple.com" class="">jfbastien@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class="">Hello WebKilters,</div><div class=""><br class=""></div>Our Chrome-y friends are considering <a href="https://groups.google.com/a/chromium.org/forum/?utm_medium=email&utm_source=footer#!msg/cxx/ow7hmdDm4yw/eV6KWL2yAQAJ" class="">the use of C++14</a>. I have to say that C++14 in WebKit has been <i class="">quite amazing</i>, and we should consider using C++17: it has many <a href="https://github.com/tvaneerd/cpp17_in_TTs/blob/master/ALL_IN_ONE.md" class="">wonderful new things</a>, some of which we already use through WTF’s re-implementation of library features. By now (<a href="http://en.cppreference.com/w/cpp/compiler_support" class="">table as witness</a>) most C++17 languages features are in clang and GCC, and MSVC isn’t doing too bad either. Language things can just come through WTF if we really want them.<div class=""><br class=""></div><div class="">So how about it?</div><div class=""><br class=""></div><div class="">JF</div></div>_______________________________________________<br class="">webkit-dev mailing list<br class=""><a href="mailto:webkit-dev@lists.webkit.org" class="">webkit-dev@lists.webkit.org</a><br class="">https://lists.webkit.org/mailman/listinfo/webkit-dev<br class=""></div></blockquote><div class=""><div class=""><br class=""></div></div></div></body></html>