Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Rather than using a GC or some borrow checking system, we shrug and say, well what can ya do?

Try different paths until someone stumbles on the One True Way™.

Plus, `if (a=4)` will emit a compiler warning of ‘statement always evaluates to true’ or somesuch and is useful in some cases like ‘if (!(a=foo())) goto error;’



> Try different paths until someone stumbles on the One True Way™.

I'm aware there isn't a perfect solution (because of Rice Theorem). But we don't need perfect, we need better than status quo (C).

> Plus, `if (a=4)` will emit a compiler warning

It's still a step down. What is better than a compiler warning that people can ignore? Prohibiting the syntax altogether.

> goto error;

This is another example of a famous chain-footgun. Most langs eschew use of goto even if it allows more flows than plain old for/while loops.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: