Re:Writing Network Drivers in Rust [pdf]
by palotasb on Thursday November 08, 2018 @10:43AM
(#18407023)
In every way? One could argue that having a GC is a disadvantage compared to Rust regardless of how good a GC it is. Main reason for that is because it might still introduce unnecessary runtime overhead.
[ Parent
| on HN ]
Re:Writing Network Drivers in Rust [pdf]
by tcoff91 on Thursday November 08, 2018 @10:57AM
(#18407118)
Also what about the data race detection stuff that rust does? A GC does not stop data races.
Re:Writing Network Drivers in Rust [pdf]
by nimmer on Thursday November 08, 2018 @10:56AM
(#18407109)
It does not.
Re:Writing Network Drivers in Rust [pdf]
by monocasa on Thursday November 08, 2018 @01:53PM
(#18408819)
GCs absolutely increase memory pressure overhead, or are so conservative that they practically lead to slow leaks. You have to keep that metadata of "what is and isn't a pointer" somewhere and that comes with a cost.
Memory pressure is a different thing. And, once again, GC is optional.
Re:Writing Network Drivers in Rust [pdf]
by monocasa on Friday November 09, 2018 @12:43PM
(#18416260)
> Memory pressure is a different thing.
No it isn't. The GC has to touch that data, which means it's cache pressure, which means it's perf pressure.
> And, once again, GC is optional.
Sure, but it's an exclusive choice between memory safety and speed. Other languages let you have your cake and eat it too in that respect (Cyclone, Rust, etc.).