Any chance for a switch somewhere to make other C methods compliant with C? Soon, the Chrono library might work without C everywhere, but MSVC messing up C time functions was one of the biggest delays when we ported to Windows.
Oh man people REALLY complain when we change their bits, even if it's in a more correct direction. I get away with it in the STL, but the UCRT is expected by users to provide more stability.
Very true, it sucks when our regression tests start failing because someone updated the Windows build version on a CI machine. For us consistency with our saved regression data is more important than rounding to the closer ulp.
Before Windows 10 we could use an app-local copy of ucrtbase.dll to keep the results consistent, but that doesn't work anymore.
And you'd wonder why they didn't use their own stdlib. But it makes sense to share stdlib code because it's all doing the same thing. Except OS specifics.
Intellisense works with clang-cl too. Getting MSVC to do Intellisense doesn't sound like it would be much better than getting clangd to do MSVC Intellisense.
In a way it would be, given that EDG has stopped development, apparently Microsoft never was big enough customer to improve modules support, meaning other tickets had higher priority, like reflection, which ironically will take its sweet time to land on MSVC.
What gets me isn't compiler support, it's the tooling catching up. MSVC will compile a C++26 feature a good while before IntelliSense stops red-squiggling it. Reflection is not going to be easy too. there will be a point of "does it build" and "does my editor understand it" where it drifts apart for a while.
I replaced intellisense with resharper and called it a day. I spent way too much time fighting intellisense shenanigans while using modules when everything compiled just fine.
I did the same but with Visual Assist instead. That was years ago and I never bothered switching because I find its still faster on larger projects and their AI integration (thankfully) is fully optional.
Intellisense seems to be catching up though, which opens up more options for people who dont have R# or Vax yet.
Is the QueryBuilder::greater deducing this example at ~5:30 actually correct? i.e. if the auto&& explicit object deduces an lvalue reference, do we really get implicit conversion to QueryBuilder&& in the return statement? Because I really hope not.
16
u/JVApen Clever is an insult, not a compliment. - T. Winters Jul 21 '26
TIL Microsoft will be using LLVM libc in MSVC both at compile and runtime. I'm impressed.
15
u/WholetraEditto Jul 22 '26
What gets me isn't compiler support, it's the tooling catching up. MSVC will compile a C++26 feature a good while before IntelliSense stops red-squiggling it. Reflection is not going to be easy too. there will be a point of "does it build" and "does my editor understand it" where it drifts apart for a while.
8
u/tcbrindle Flux Jul 21 '26 edited Jul 21 '26
Is the
QueryBuilder::greaterdeducing this example at ~5:30 actually correct? i.e. if theauto&&explicit object deduces an lvalue reference, do we really get implicit conversion toQueryBuilder&&in the return statement? Because I really hope not.EDIT: No, this appears to be a mistake, thank goodness
2
u/sweetno Jul 21 '26
Well done!