Hacker News

ibobev
C++26: Trivial infinite loops are no longer undefined behaviour sandordargo.com

Aurornis8 minutes ago

I never would have guessed that the unreachable() function would get executed in that example. Probably not something you’d encounter in practice, though I have seen some weird things happen with layers of #ifdef

MiroslavPokorny14 hours ago

Breadcrumbs for "blog", "year", "month" etc are broken and give 404s :(

One can browse other blog entries so it really doesnt matter too much.

adzm3 minutes ago

as an aside, i've always preferred the zoidberg for (;;) to while(true)

adzm4 minutes ago

i have never before thought that a function could 'fall through' to another function. why does this behavior even exist?

oleganza2 minutes ago

Why is null-terminated C string considered a "billion dollar mistake", but UB isn't?

BobbyTables25 minutes ago

TLDR: For almost 1/6 of a century, the C++ standards broke the simplest infinite loop and only just recently fixed it.

Idiots!

Don’t they really that people write real programs to solve real problems? This isn’t a theoretical academic exercise!

hn-front (c) 2024 voximity
source