Reported by Jesse Towner Mar 09 at 06:59 PM windows 10.0visual studio 2017 version 15.6editorC++fixed in: visual studio 2017 version 15.8 preview 3

Android NDK r15c uses Clang 5.0 which supports all of C++14 and is C++17 feature complete (unfortunately, the libc++ runtime that ships in Clang/LLVM 5 only has partial C++17 library features). However, in the properties for native Android projects Visual Studio 2017 15.6.1 the available options for the C++ Language Standard setting hasn't been updated to reflect the latest capabilities of the compiler.

The option "C++14 (GNU Dialect) (-std=gnu++1y)" should be changed to use -std=gnu++14 instead of -std=gnu++1y. Furthermore, a new option should be added "C++17 (GNU Dialect) (-std=gnu++1z)" to enable the available C++17 support.

Currently, it's possible to work around this issue by adding -std=gnu++1z to AdditionalOptions in the Command Line pane of the Properties dialog box, and defining the _LIBCPP_STD_VER to 15 or greater. One might argue you don't want to enable this language mode if it doesn't fully support it, but really MSVC++ 2017 isn't any different in this regard--it too has partial C++17 support (albiet with more library features), yet allows you to make use of what's there.

It also appears that Intellisense for Android can't recognize C++17 syntax. It has trouble on structured bindings for instance and selection statement initializers (new if and switch syntax).

It would be a major boon if the C++14 and C++17 experience in MSVS for Android using NDK 15c & Clang 5 could be improved, especially since we're at a point where a lot of developers are looking at migrating to these newer language standards given the widespread availability of Clang/LLVM 5 based toolchains on a number of different platforms (not just Android).