This sound like a wild and very contrived argument. Both because that memory leaks are normal is types languages - and does usually not matter in most serious

This sound like a wild and very contrived argument. Both because that memory leaks are normal is types languages - and does usually not matter in most serious applications - and because this class of errors is usually not what types catch. Types have value when you 1) refactor and 2) have multiple people working on a code base. The error you see when you don't have types is something like a BadArityError.