bored

> 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/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

Here you don't check the return value of calloc(): https://github.com/AndrewBelt/bored/blob/master/src/map.c#L3... and then access it: https://github.com/AndrewBelt/bored/blob/master/src/map.c#L4... Here if realloc() fails, you'll have a memory leak and, again, accessing NULL later: https://github.com/AndrewBelt/bored/blob/master/src/priq.c#L... There is also integer overflow: alloc is int, so if it becomes greater than 2^31-1, it may wrap around [I think signed int behaviour in C is undefined in this case], and you'll allocate fewer bytes than needed, leading to buffer overflow.