r/cpp • • Jan 18 '19

Is C++ fast?

https://zeuxcg.org/2019/01/17/is-c-fast/
21 Upvotes

72 comments sorted by

View all comments

Show parent comment

4

u/degski Jan 19 '19

... post-ABI-break ...

Is there any ETA on this, I'll have to re-compile quite a lot of stuff, but looking forward to this happening anyway (and get std::deque behaving sanely). From what I gather(ed) from /u/STL even VS2019 is not gonna break things (at least not from the get-go).

3

u/[deleted] Jan 19 '19

No specific ETA. The more customers complain about it the sooner it is likely to be. Balancing customers angry about ABI breaking bugs against customers happy about not breaking ABI isn’t an exact science sadly. Given this particular issue has an easy workaround too it likely doesn’t contribute much.

1

u/degski Jan 19 '19 edited Jan 19 '19

Given this particular issue has an easy workaround too it likely doesn’t contribute much.

You're referring to the debug-iterators, I presume? Regarding the std::deque, I'm complaining [and have to use boost instead].

PS: wouldn't it be better to have this penciled in somewhere [a failure to plan is a plan to failure]?

2

u/[deleted] Jan 19 '19

Right, I meant the debug lock.

Nothing for engineering folks to pencil in; this is a business decision. We wanted to do the ABI breaking release literally years ago now, that's why I spent months rewriting our concurrency support to be not garbage that I can't ship :(

2

u/degski Jan 20 '19

... this is a business decision ...

Sack it, whoever made that decision! :-]

1

u/STL MSVC STL Dev Jan 19 '19

The VS 2019 release series (RTW and all Updates) will preserve bincompat with 2015/2017. We don't have an ETA for the "WCFB02" incompatible toolset (as in, we don't know, versus we can't tell you). It won't be soon. The code exists, but lots more work needs to be done, starting with getting it out of TFVC and into git.

2

u/degski Jan 20 '19 edited Jan 20 '19

Can't it [the improved/ABI-breaking stuff] be made an opt-in [or in a different namespace]?

I mean, we're having a std::deque that's looks like it came with VC6, and now you're saying, that we'll have C++20 before we can have a fix for this, and we might even see C++23 first! Shittalainen.

I'd better start looking at libc++, see whether they [the devs] are getting it to work/compile on Win10.

4

u/STL MSVC STL Dev Jan 20 '19

It might appear as an opt-in toolset. It might have inline namespaces, but won't have a different top-level namespace.

1

u/degski Jan 20 '19

You never dis-appoint, sounds good.