News for hackers. Stuff that matters.

A comment on Go GC: Solving the Latency Problem in Go 1.5. Parent comment

Re:Go GC: Solving the Latency Problem in Go 1.5 by pjmlp on Thursday July 09, 2015 @04:03AM (#9856684)
Besides Rust, only Cyclone, ATS and ParaSail offer similar ways of memory management[0].

It would be nice if Rust becomes mainstream, but it is still a very long way to go.

[0] D is adding some support for it as well.

[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by Negitivefrags on Thursday July 09, 2015 @04:09AM (#9856699)
C++ also qualifies. std::unique_ptr and std::shared_ptr together form a very nice automatic memory management system.
[ Parent | on HN ]
Re:Go GC: Solving the Latency Problem in Go 1.5 by pjmlp on Thursday July 09, 2015 @04:32AM (#9856757)
C++ doesn't enforce you to use them, while the other languages have their memory models enforced by the compiler, hence why I left C++ out.

In large teams no one can prevent the cowboy coder on the team to go C style on a large C++ codebase, specially when code reviews and static analysis are not used.

[ Parent | on HN ]