3 ms·
I don't use Go, but I thought that nulls in it were memory safe (i.e. they abort rather than corrupt); am I wrong? If I'm not wrong, this is a non-sequitor on
by aidenn0 10y ago
I don't use Go, but I thought that nulls in it were memory safe (i.e. they abort rather than corrupt); am I wrong?
If I'm not wrong, this is a non-sequitor on a post about Common Lisp as Common Lisp is untyped, but (by default; some implementations allow you to disable safety) safe.
- lokedhs 10y agoTechnically Common Lisp is optionally typed. You can add static typing if you feel like it, and it can give you a significant performance boost when you do. Fortunately, I don't have to bother with it most of the time since the amount of code that is time-critical enough for it to matter is very small.