Re: [webkit-dev] C++17 is here. Should we use it?

On Tue, May 7, 2019 at 1:46 PM, Konstantin Tokarev wrote: Note that since we have to support libstdc++ 6.x, most of C++17 standard library features () should be disallowed. Those include std::filesystem, std::string_view, etc. Core language features should be fine. With my suggested

Re: [webkit-dev] C++17 is here. Should we use it?

On Tue, May 7, 2019 at 1:53 PM, Alex Christensen wrote: If you have a minimum-requirements system that you want to keep building, put build infrastructure on build.webkit.org so we can see when things break. We already have stable release bots to test the lowest-supported configurations,

Re: [webkit-dev] C++17 is here. Should we use it?

If you have a minimum-requirements system that you want to keep building, put build infrastructure on build.webkit.org so we can see when things break. We plan to actively push to update requirements again in 2021. > On May 7, 2019, at 11:46 AM, Konstantin Tokarev wrote: > > > > 07.05.2019,

Re: [webkit-dev] C++17 is here. Should we use it?

07.05.2019, 16:53, "Michael Catanzaro" : > Since there were no objections, I've updated the policy on the wiki: > > https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy > https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement Note that since we have to support libstdc++ 6.x, most of C++17

Re: [webkit-dev] Exciting JS features (class fields) in need of review :)

Hi all, last February we got a thorough review of the class fields patch, and have been updating it pretty frequently since. We think it's ready to be reviewed again. Hopefully we'll manage to either land this first stage of the feature, or receive enough new feedback to keep working on it. The

Re: [webkit-dev] C++17 is here. Should we use it?

Since there were no objections, I've updated the policy on the wiki: https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy https://trac.webkit.org/wiki/WebKitGTK/GCCRequirement Michael ___ webkit-dev mailing list webkit-dev@lists.webkit.org