[vtsrh]

Well the solution is simple:

  return (x+0U)<<16 | (y+0U);

Would it be insane to have a inline library for every arithmetic operation, that would handle such cases and offer addition optional functionality?

[lmm]

The intersection of people who are willing to rewrite all their arithmetic to use such a library with people who are not willing to switch to a non-C language is rather small.

[vtsrh]

Keep the old code, instead just start using it for new one.

[lmm]

Most projects still written in C are those that make extensive use of C libraries. Making the application code immune doesn't actually reduce the vulnerability surface much - much of the vulnerability comes in the libraries the application calls.

[vtsrh]

Use it for new code. Libraries are written too.

[lmm]

Libraries are usually older than the applications that use them. New libraries can be, and often are, written in new languages.

[vtsrh]

https://news.ycombinator.com/item?id=9885478

Looks like you hit an infinite loop. Better luck next time.