u/TemplateRex

To me it’s at least operator<=>, concepts and std::format, so C++20.

Multi precision uses sign/magnitude (I.e. positive and negative zero), not the usual 2’s complement. It can’t represent -2¹²⁸

But not constexpr and not noexcept

Great talk! I wonder, is it possible to reflect over the header implementation of <vector> and actually make use of its helper functions for growth, insertion etc.? Like your function grow() screams out to be an actual implementation primitive that you would want to re-use.

Germany lost WW1 without a British or French soldier on German soil. No need to win the land back, just cause economic collapse.

Nice! Chrono for integers :-)

Uuuuuuuuuuuunbelievable

https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/divmodnote-letter.pdf Is a nice, short paper listing various definitions consistent with that invariant.

Finally, size_t literals in my lifetime! (5 year after being voted into the Standard, yay!).

Thanks for the explanation!

But can’t the if be made if constexpr here since is_constant_evaluated is constexpr?

They have segways in the Silo?, LoL (Auto-correct of “segue” perhaps?)

I think there is a passage in Stepanov's Elements of Programming where he discusses that ìn principle std::begin (address of), std::end (one beyond address of) and std::empty (equal to zero) could be defined for all objects of any type, so that you could iterate over anything.

Wait, wut? Reasoned debate on Reddit and an STL maintainer changing his mind! Kittens are purring all over the world :-)

Why not open source the compiler and let the pull requests come in? ;-)

That shot at the gas station, with Yas looking at that poor woman with the kids in the back. Very reminiscent of the Sopranos scene where Christopher is contemplating on whether to run off with Adriana or not. https://www.youtube.com/watch?v=LYdeflJaOZI

I spent 2 weeks in the Swiss Alps in the summer of 2019. In contrast to Austria where cash is still pervasive, I never needed any Swiss cash at all, not even for icecream on top of mountains.

it was blackjack, could theoretically have a small +EV with good counting. Not that he was capable of that given his condition...

But which parts? Reading through filenames that don't exist?

Safety for <filesystem> could be massively improved with a very simple change to the standard in C++

What simple change would improve <filesystem>?

I guess there is room for automating this as a toolbar button directly from VS Studio on every ICE? Not submitting perhaps, but preparing the preprocessed repo?

Thanks so much, very much appreciated! I've submitted the bug along with the preprocessed repo (https://developercommunity.visualstudio.com/t/ICE-on-valid-C23-code-tested-with-gcc/10694428)

Could you point me to instructions on how to preprocess? I'm a Windows dev noob (using Linux). I'm building in VS Studio (as well as VSCode) using cmake (building with the usual "cmake .. && cmake --build .") and I get an immediate ICE without other errors.

(not modules related, but an ICE nevertheless). I have a C++23 project on GitHub that compiles and runs cleanly on gcc 14 and clang 18 but ICEs on MSVC 17.10. I suspect that it is caused by a known bug with auto NTTP. The suspected bug (and a host of related items) has had 4 years of inaction on Developer Community. What is the best way to submit this ICE as a bug report?

there's a great book The Stars are Not Enough with a very nice overview of the work/life tradeoffs that scientists make