Programmers can make and gradually change these choices within a single language and ecosystem: - Dynamically vs statically typed (vs theorem prover) - Garbage collected vs ownership-based memory management Python, OCaml, and Rust merge (in spirit) to become this language.https://twitter.com/smdiehl/status/1342886946775965697 …
-
-
Ah good point, although, you can make that happen with a ref-counting GC: allocate an object (with the appropriate finalizer) at the beginning of the scope, and then drop the object when you exit the scope.
-
On the surface it seems like this would work, because if you had any cascading destructors, they would naturally be acyclic. But perhaps there’s a lurking nasty subtlety
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD