2 ms·
Because atomic reference counting has much worse throughput than tracing GC. This has been known for a long time. It makes sense for Swift because of Swift's u
by pcwalton 11y ago
Because atomic reference counting has much worse throughput than tracing GC. This has been known for a long time.
It makes sense for Swift because of Swift's unique constraints—interoperability with an atomic-reference-counted world (Objective-C) and, less importantly, mobile UIs putting demands on latency. But most applications would be better off with a tracing GC.
- AlisdairO 11y ago> Because atomic reference counting has much worse throughput than tracing GC. This has been known for a long time. I know this to be true for ubiquitously heap allocated systems, but I'm curious if this has been studied extensively for stack+heap reference counted systems, where only a relatively small number of items are heap allocated? Seems like reference counting would gain in this kind of environment, as the stack effectively gives you many of the advantages generational gcs enjoy from their nursery, and you don't have to worry about write boundaries, tracing and the like.