Thread

1. Aardwolf · 1789766294 · focus · HN ↗

   > the implementation may assume any thread will eventually do one of the following: terminate, call a library I/O function, access a volatile glvalue, or perform a synchronization or atomic operation

   Why is that rule needed? I could make my for loop try to solve the halting problem and it'll never finish either, circumventing that rule

   1. mitxela · 1789778212 · focus · HN ↗

      So the compiler can merge two computation loops without proving termination.

Unofficial Hacker News client; not affiliated with Y Combinator.