4 ms·
> getting a mechanical check on memory safety for the price of some extra language verbosity is obviously worth it IMO But a GC'd language doesn't require the
by amelius 3y ago
> getting a mechanical check on memory safety for the price of some extra language verbosity is obviously worth it IMO
But a GC'd language doesn't require the extra verbosity.
- buildartefact 3y agoAnd you pay for that in performance
- kaba0 3y agoWhat performance? That’s not a single thing. Do you pay in throughput or latency? It certainly has a price but it is waaay too overblown in many discussions. What it mostly does entail is a slightly larger p99 latency. Where it actually matters is entirely another question.
- zbentley 3y agoGC has little to do with it. The borrow checker as a developer tool has much more to do with preventing concurrency bugs and unexpected mutation than it does with memory management. "As a developer tool" is doing some work in that sentence though. As a language implementation characteristic, the checker can help inform (or, more accurately, ensures that code is written in a way that informs) memory management decisions.