Hacker News Reader

> And no, usual Internet advice of “MSVC sucks, use Clang”

Given that this talks about a problem in the Microsoft standard library, wouldn't the usual internet advice be "use clang, and also llvm's libc++"? If clang just compiles the same slow code as msvc, it won't magically make it fast.

View on HN

If you're building for windows, interop may require that you also use the msvc standard library.

It's honestly not really true on windows. Since for the longest time the msvc ABI was unstable people are used to interop through C APIs, or rebuilding everything. I personally build all my stuff with libc++ and it works fine.

If you also want to use libraries that are built against MS STL, then you can't really use libc++. Of course if you can build everything with libc++, that's fine. That's how Chromium is built, AFAIK.

That depends, on windows multiple standard libraries (even libc) can cohabit in the same process (but you have to be careful to, say, not free something in a different dll than the one which allocated it). If you are careful with that and aren't exchanging standard library types across library boundaries there won't be issued.

Reply on news.ycombinator.com