> I've written lots of C and never had problems with buffer overruns, bounds checking, double frees, and other memory issues. Typically at a glance in one's cod

> I've written lots of C and never had problems with buffer overruns, bounds checking, double frees, and other memory issues. Typically at a glance in one's code, I can tell when behavior may be undefined, and once someone has a little experience, they can avoid undefined behavior altogether. Why does so much work go into fixing these problems? In other words, what are some examples of use cases of a stricter language like this, that would be too complicated for human eyes to quickly verify? Some memory issues with code you might be familiar with... From your own repo. https://github.com/AndrewBelt/game_of_life/blob/master/src/grid.c https://github.com/AndrewBelt/game_of_life/blob/master/src/g... Not checking for return values is not a great idea. Your code blows up phenomenally with certain "width" and "height" values. It does check against negative grid sizes, but that's not enough (https://github.com/AndrewBelt/game_of_life/blob/master/src/gol.c https://github.com/AndrewBelt/game_of_life/blob/master/src/g...)! With suitable width & height it'd also gladly free a "grid" it never allocated. Of course it crashes long before that happens. Ok, so it was cloned from someone else's repo, and you never got around cleaning it up. Let's see... https://github.com/AndrewBelt/bored/tree/master/src https://github.com/AndrewBelt/bored/tree/master/src Ok, still not checking return (SDL, etc.) values. Debug build asserts are better than nothing -- didn't bother to check how your build is configured.