Daniel Marks on Nostr: nprofile1q…lkxk4 I am curious about programming "discipline" to avoid things like ...

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqp450apv3j8jmqjct3ddfklzusxyfkkyqpzxx4p33u099xjzvfwwsjlkxk4 (nprofile…kxk4) I am curious about programming "discipline" to avoid things like stack overflows, invalid or null pointer dereferences, etc. Does curl use fixed array sizes, especially for arrays allocated on the stack? Is there bounds checking, and do lint-tools check bounds at compile time? Are freed pointers assigned to NULL to prevent referencing deallocated memory? There are tradeoffs between the Rust-style borrow checker requirements, and the flexibility of manual data structure management.