Replying to
@shac@ioc.exchange
@shac@ioc.exchange This is a fine enough definition of memory safe, but not the one in common use. People typically consider the likes of Java, Python, Go and JavaScript to be memory safe, even though they all have variations of null pointer dereference exceptions and use after free exceptions (e.g exceptions due to writing to a closed stream). It's generally considered "memory safe" because the result is a controlled crash rather than "undefined behavior" where anything can (and will) happen.