4 ms·

VS 2015 doesn't (fully) support Expression SFINAE. Looks like VS 2017 will: https://blogs.msdn.microsoft.com/vcblog/2016/11/16/sfinae-update/ https://blogs.msdn

by krona 10y ago

VS 2015 doesn't (fully) support Expression SFINAE. Looks like VS 2017 will: https://blogs.msdn.microsoft.com/vcblog/2016/11/16/sfinae-update/ https://blogs.msdn.microsoft.com/vcblog/2016/11/16/sfinae-up...

hellofunk 10y ago
But in 2017, there will be another significant new standard, C++17. I wonder if VS will not support it until 2022, if they remain 6 years behind on new language standards?
- pjmlp 10y ago
  People like to complain about VS, but they are quite good in what concerns commercial C++ compilers. http://en.cppreference.com/w/cpp/compiler_support http://en.cppreference.com/w/cpp/compiler_support And C++ compiler support page doesn't provide information about the likes of TI and similar embedded OEMs, otherwise that reddish colour would be even bigger.
  - adrianN 10y ago
    In the embedded world you can consider yourself lucky if you get a halfway working c++98 compliance.
- krona 10y ago
  I agree with your general point, but frankly the only feature of C++17 I'm interested in is await/resume and that's already supported in VS 2015.
  - gpderetta 10y ago
    Await/resume won't be in c++17, as it is very contentious. It will be first released as a Technical Report.
- ntauthority 10y ago
  VS2017 already is quite far into supporting C++14/C++17 features, except that expression SFINAE and extended constexpr were not viable to implement on the original (dated) compiler frontend and therefore the past years have been spent on rewriting large portions of the compiler. The VC team blog provides fairly decent information with regards to reasoning and progress behind this.
- Scea91 10y ago
  C++17 won't be that significant. All of the major features have been postponed to later revisions.
fetbaffe 10y ago
Yes, you are right. And the table I linked to actually said No on Expression SFINAE for Visual Studio 2015 if you read it carefully, which I did not.
gpderetta 10y ago
I believe that VS still doesn't do two phase lookup. Not sure whether it will be fixed in 2017.

by krona 10y ago

hellofunk 10y ago

But in 2017, there will be another significant new standard, C++17. I wonder if VS will not support it until 2022, if they remain 6 years behind on new language standards?

pjmlp 10y ago
People like to complain about VS, but they are quite good in what concerns commercial C++ compilers. http://en.cppreference.com/w/cpp/compiler_support http://en.cppreference.com/w/cpp/compiler_support And C++ compiler support page doesn't provide information about the likes of TI and similar embedded OEMs, otherwise that reddish colour would be even bigger.
- adrianN 10y ago
  In the embedded world you can consider yourself lucky if you get a halfway working c++98 compliance.
krona 10y ago
I agree with your general point, but frankly the only feature of C++17 I'm interested in is await/resume and that's already supported in VS 2015.
- gpderetta 10y ago
  Await/resume won't be in c++17, as it is very contentious. It will be first released as a Technical Report.
ntauthority 10y ago
VS2017 already is quite far into supporting C++14/C++17 features, except that expression SFINAE and extended constexpr were not viable to implement on the original (dated) compiler frontend and therefore the past years have been spent on rewriting large portions of the compiler. The VC team blog provides fairly decent information with regards to reasoning and progress behind this.
Scea91 10y ago
C++17 won't be that significant. All of the major features have been postponed to later revisions.

fetbaffe 10y ago

Yes, you are right. And the table I linked to actually said No on Expression SFINAE for Visual Studio 2015 if you read it carefully, which I did not.

gpderetta 10y ago

I believe that VS still doesn't do two phase lookup. Not sure whether it will be fixed in 2017.