Yes, let’s ignore the quite literally millions of examples of prior art for memory bugs in C/C++ programs because you believe you’ve managed to build a single-threaded CLI calculator that doesn’t have any.
I know how to call `strcpy` safely. Are we clear to put that back into the Linux kernel then?
I know how to call `strcpy` safely. Are we clear to put that back into the Linux kernel then?