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 …
Yes, like that. The PL challenge is how to automatically lift an API designed eg for ownership into one that works with garbage collection. For example, guard pattern (eg releasing mutex in destructor) is hard without ownership.
-
-
Well, GC is more general so you could just “forget” about the ownership and let the GC rediscover it. It’s easy to tack finalizers onto objects to be able to call some arbitrary code when an object is collected. But perhaps the performance of this would be unacceptable?
-
(as reference counting techniques become more efficient, we may see some of these performance issues with GC become much less of a problem.)
- 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