3 ms·
It's still apples to oranges, because Rust will only ever have an fine-grained optional GC (you choose what objects s to pop into the GC), not a pervasive one.
by Manishearth 11y ago
It's still apples to oranges, because Rust will only ever have an fine-grained optional GC (you choose what objects s to pop into the GC), not a pervasive one.
- Ericson2314 11y agoWell the second step is a make an allocator crate that puts GC in as the system allocator for std.
- Manishearth 11y agoAs far as Java is concerned, _still_ apples-to-oranges since Rust doesn't pervasively mallocate either. Go would be an ok comparison. I suspect Go would come out on top, since it actually tries to avoid GCing things, whereas the Rust compiler wouldn't even be aware that there is a GC going on and wouldn't do any analysis.
- Ericson2314 11y agoI mean compare the same rust programs, with jemalloc vs with GC.
- Manishearth 11y agoAh, okay. That can work.