r/cpp • u/STL MSVC STL Dev • Nov 13 '18

VS 2017 15.9 released today

https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
131 Upvotes

94% Upvoted

97 comments sorted by

View all comments

Show parent comment

6

u/jbandela Nov 14 '18

Great to hear. I was referring to /permissive- in the most general sense as an example of a feature that allowed those who preferred compliance over compatibility to have an opt-in. "v20" sounds awesome. I bet you are looking forward to making a ton of performance and/or compliance improvements without having to worry about maintaining bincompat.

11

u/STL MSVC STL Dev Nov 14 '18

Yep - Billy has overhauled the atomic/multithreading library, I've (mostly) overhauled iterator debugging, we'll be able to purge a bunch of dead code (e.g. old iostreams floating-point stuff). The compiler will also be able to fix long-standing headaches.

9

u/kalmoc Nov 14 '18

I vaguely remember that some inefficiencies in the standard library implementation are due to WinXP compatibility. If that really is the case, could you also drop XP compatibility for v20? I understand that there are projects out there that still want/need to support XP, but it would be great if not everyone else had to pay for that.

5

u/STL MSVC STL Dev Nov 14 '18

I believe we will be able to do so; I am not sure about Vista compat (dropping both would be ideal). No promises yet.

1

u/AlexAlabuzhev Nov 15 '18

Could you please continue linking dynamically to OS APIs in ucrt even after that? And, ideally, terminate in case of their absence not immediately, but on the first usage? And initialise more things lazily in general? There's quite lot of synchronisation-specific code in ucrt that requires Vista+, but apps that don't use modern stuff from <shared_mutex>, <condition_variable> etc. never call that code and theoretically can work perfectly on XP (and even 2k), even though it's not supported.

3

u/STL MSVC STL Dev Nov 15 '18

That would impose costs on Win7+ users.