Go GC: Prioritizing low latency and simplicity

Re:Go GC: Prioritizing low latency and simplicity by mehrdada on Monday August 31, 2015 @10:33PM (#10150373)

I merely used automatic reference counting as one alternative automatic memory management technique. Rust, as I understand it, uses a similar alternative, which is, at least on paper, similar to enforcing a max refcount of one on pointers, statically. I'm far from a Rust expert so feel free to correct me if I'm wrong.

[ Parent | on HN ]

Re:Go GC: Prioritizing low latency and simplicity by kibwen on Monday August 31, 2015 @10:53PM (#10150448)

I'd say that "reference counting" implies a dynamic/runtime component, which is not how Rust manages memory (unless you're specifically using the `Rc` pointer in the stdlib).

I think it's important to be clear here because Swift and Objective-C rely on a technology known as "Automatic Reference Counting" (ARC), which does imply the usual dynamic cost of reference counting.

[ Parent | on HN ]