search for: compiler_support

...s/papers/2013/n3651.pdf> Member initializers and aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> A bunch of new constexpr language and library features Various other language and library features See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. Toolchains We’re currently mandating: Clang 3.1 (released 2012/05) Apple Clang 3.1 (released 2012/05) GCC 4.8 (released 2013/...

...low constant evaluation for all non-type template arguments > - Fold Expressions > - Unary fold expressions and empty parameter packs > - __has_include in preprocessor conditional > - Differing begin and end types in range-based for\ > > From: https://en.cppreference.com/w/cpp/compiler_support > <https://en.cppreference.com/w/cpp/compiler_support> > > The only thing that’s really nice are fold expressions, and I hope > they’re not buggy in GCC 6. > > Otherwise the list is missing a good amount for C++17 language > features, and brings up the discussion of which...

...tializers and aggregates (NSDMI) > <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> > - A bunch of new constexpr language and library features > - Various other language and library features > > See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for > details. > > Of these, I think polymorphic lambdas are the big feature. Of course, just > like Almost Always Auto, we should use such things only where it makes > sense. > > > *Toolchains* > > We’re currently mandating: > > - Clang 3.1 (*released 201...

...tializers and aggregates (NSDMI) > <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> > - A bunch of new constexpr language and library features > - Various other language and library features > > See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for > details. > > Of these, I think polymorphic lambdas are the big feature. Of course, just > like Almost Always Auto, we should use such things only where it makes > sense. > > > *Toolchains* > > We’re currently mandating: > > - Clang 3.1 (*released 201...

...ializers and aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>> A bunch of new constexpr language and library features >>> Various other language and library features >>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. >>> >>> Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. >>> >>> >>> Toolchains >>> >>> We’re currently mandati...

...- u8 character literals - Allow constant evaluation for all non-type template arguments - Fold Expressions - Unary fold expressions and empty parameter packs - __has_include in preprocessor conditional - Differing begin and end types in range-based for\ From: https://en.cppreference.com/w/cpp/compiler_support <https://en.cppreference.com/w/cpp/compiler_support> The only thing that’s really nice are fold expressions, and I hope they’re not buggy in GCC 6. Otherwise the list is missing a good amount for C++17 language features, and brings up the discussion of which GCC version is the minimum we ma...

...aggregates (NSDMI) <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>>> A bunch of new constexpr language and library features >>>> Various other language and library features >>>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for details. >>>> >>>> Of these, I think polymorphic lambdas are the big feature. Of course, just like Almost Always Auto, we should use such things only where it makes sense. >>>> >>>> >>>> Toolchains >>>> >>>...

...p://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>>> - A bunch of new constexpr language and library features >>>> - Various other language and library features >>>> >>>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for >>>> details. >>>> >>>> Of these, I think polymorphic lambdas are the big feature. Of course, >>>> just like Almost Always Auto, we should use such things only where it makes >>>> sense. >>>> >>>> >>&g...

....org/jtc1/sc22/wg21/docs/papers/2013/n3653.html> >>>>> - A bunch of new constexpr language and library features >>>>> - Various other language and library features >>>>> >>>>> See CppReference <https://en.cppreference.com/w/cpp/compiler_support> for >>>>> details. >>>>> >>>>> Of these, I think polymorphic lambdas are the big feature. Of course, >>>>> just like Almost Always Auto, we should use such things only where it makes >>>>> sense. >>>>> &gt...

If it's the only thing we can agree then I'll take it, but I just worry that 3 years from now we're going to start another 3 year discussion, so that any actual move to C++17 would end up taking double the time. Are the issues specific to C++17 additions to the standard library? What if you allow C++17 language features but not C++17 library features? I'm guessing this is too

...low constant evaluation for all non-type template arguments > - Fold Expressions > - Unary fold expressions and empty parameter packs > - __has_include in preprocessor conditional > - Differing begin and end types in range-based for\ > > From: https://en.cppreference.com/w/cpp/compiler_support > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > Otherwise the list is missing a good amount for C++17 language features, > and brings up the discussion of which GCC version is the minimum we > mandate. I’d rather avoid th...

...- u8 character literals - Allow constant evaluation for all non-type template arguments - Fold Expressions - Unary fold expressions and empty parameter packs - __has_include in preprocessor conditional - Differing begin and end types in range-based for\ From: https://en.cppreference.com/w/cpp/compiler_support The only thing that’s really nice are fold expressions, and I hope they’re not buggy in GCC 6. Otherwise the list is missing a good amount for C++17 language features, and brings up the discussion of which GCC version is the minimum we mandate. I’d rather avoid that discussion. Let’s assume GCC 6...

...l non-type template arguments > > - Fold Expressions > > - Unary fold expressions and empty parameter packs > > - __has_include in preprocessor conditional > > - Differing begin and end types in range-based for\ > > > > From: https://en.cppreference.com/w/cpp/compiler_support > > > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > > > Otherwise the list is missing a good amount for C++17 language features, and > brings up the discussion of which GCC version is the minimum we mandate. I’d...

...- Fold Expressions >> >> - Unary fold expressions and empty parameter packs >> >> - __has_include in preprocessor conditional >> >> - Differing begin and end types in range-based for\ >> >> >> >> From: https://en.cppreference.com/w/cpp/compiler_support >> >> >> >> The only thing that’s really nice are fold expressions, and I hope they’re >> not buggy in GCC 6. >> >> >> >> Otherwise the list is missing a good amount for C++17 language features, and >> brings up the discussion of which GCC...

...l non-type template arguments > > - Fold Expressions > > - Unary fold expressions and empty parameter packs > > - __has_include in preprocessor conditional > > - Differing begin and end types in range-based for\ > > > > From: https://en.cppreference.com/w/cpp/compiler_support > > > > The only thing that’s really nice are fold expressions, and I hope they’re > not buggy in GCC 6. > > > > Otherwise the list is missing a good amount for C++17 language features, > and brings up the discussion of which GCC version is the minimum we > mandate....