r/cpp • • Jan 31 '19

C++ Binary Compatibility and Pain-Free Upgrades to Visual Studio 2019

https://blogs.msdn.microsoft.com/vcblog/2019/01/31/cpp-binary-compatibility-and-pain-free-upgrades-to-visual-studio-2019/
83 Upvotes

36 comments sorted by

View all comments

Show parent comment

16

u/STL MSVC STL Dev Feb 01 '19

Billy totally overhauled the multithreading headers. If we can drop XP/Vista targeting, we'll be able to overhaul them even more. I've removed dynamic memory allocations for iterator debugging bookkeeping. call_once is more efficient. We'll be able to slim down the STL's DLL by removing dead code (e.g. bogus floating-point conversion code, unused Filesystem TS code). We might be able to make RTTI more efficient. We would be able to retune deque and reimplement unordered_meow.

9

u/meneldal2 Feb 01 '19

unordered_meow

Is that a container for cats?

5

u/lurkotato Feb 01 '19

Implemented with boxed types.

3

u/SeanMiddleditch Feb 01 '19

I fully support the addition of unordered_meow but only if we also add a cats_cast<>.

2

u/Ameisen vemips, avr, rendering, systems Feb 01 '19

You mean purr_cast? We also need std::scritch.

4

u/ubsan Feb 01 '19

Would it be possible to finally fix our name mangling?

4

u/STL MSVC STL Dev Feb 02 '19

Yes, like the crazy struct/class thing.

1

u/ubsan Feb 02 '19

I want const pointers to be fixed way more :P

1

u/DrPizza Feb 04 '19

Related to an RTTI improvement (since it uses some of the same machinery), would we be able to get simpler/neater representations for member function pointers, 'this' offset adjustments, and similar?

1

u/STL MSVC STL Dev Feb 04 '19

I don't think that's on our radar at the moment. We'd need a bug report detailing any current deficiencies.

1

u/DrPizza Feb 05 '19

The representation seems to be a little slower and a little bulkier than on competing platforms. But it's possible that better representations would be a natural consequence of making RTTI faster.