;; -*- eval: (message "arbitrary code") -*-
any mode associated with a file extension should be at least as secure against code execution.1,142 karma · joined April 8, 2010
;; -*- eval: (message "arbitrary code") -*-
any mode associated with a file extension should be at least as secure against code execution.</s>
The upsides of the definition you gave are that it's simple, well defined, and maximally precise (nothing that is safe to collect is considered live)
The significant downside to this definition is that it's uncomputable. To know if memory is used requires knowing if a loop halts.
The second definition of memory leak is "unreachability" which is a bit harder to nail down. It's a conservative approximation of the first definition, but is more popular because it's computable, and it's practical to write programs with or without GC that don't leak
enum List<T> { case empty; indirect case cons(T, List<T>) }On a less serious note. This sentence should be something a fiction writer knows will only end in trouble for humanity:
> I especially challenge someone to find a "self-awareness" vector that isn't contaminated by ... human emotion!