Thread

C++26: Trivial infinite loops are no longer undefined behaviour

173 points · 290 comments · ibobev

ameliaquining · 1789746941 · focus · HN ↗
The article, most unfortunately, doesn't explain why anyone would want infinite loops to be UB in the first place. I found this explanation: <a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1528.htm" rel="nofollow">https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1528.htm
1. omoikane · 1789747149 · focus · HN ↗
  The article mentions it's a halt-on-error pattern:
  <a href="https://www.sandordargo.com/blog/2026/09/16/cpp26-trivial-infinite-loops#:~:text=But%20why%20would%20anyone%20write%20while%20(true)%3B%20in%20the%20first%20place%3F" rel="nofollow">https://www.sandordargo.com/blog/2026/09/16/cpp26-trivial-in...
  Edit: sorry, missed the UB bit.
  1. pseudohadamard · 1789806452 · focus · HN ↗
    One minor nit, it's not halt-on-error, it's restart-on-error since the watchdog then restarts the system. The technical term for this is rejuvenation and it's standard practice in SCADA and similar to deal with this-shouldn't-happen error conditions.

Unofficial Hacker News client; not affiliated with Y Combinator.