News for hackers. Stuff that matters.

A comment on Go’s march to low-latency GC. Parent comment

Re:Go’s march to low-latency GC by weberc2 on Wednesday July 06, 2016 @04:30PM (#12045691)
I think you missed the bit where he said "more intelligent compiler". The compiler is the bit that does the bookkeeping, only in Rust (and evidently Swift--I haven't played with it much) it's done statically, ahead of time rather than at runtime.

That said, I think Go is a much more practical language than Rust for most problems. That said, I'm still very excited about Rust.

[ Parent | on HN ]
Re:Go’s march to low-latency GC by coldtea on Wednesday July 06, 2016 @09:24PM (#12046953)
>I think you missed the bit where he said "more intelligent compiler"

Also known as "sufficiently smart compiler": http://c2.com/cgi/wiki?SufficientlySmartCompiler

[ Parent | on HN ]
Re:Go’s march to low-latency GC by weberc2 on Thursday July 07, 2016 @12:21PM (#12050290)
These are different things. A sufficiently smart compiler is a hypothetical compiler that could theoretically optimize a high level language so that it could be faster than some low level language. This isn't what we're talking about here--we're talking about the concrete ability of the Rust compiler to preclude certain classes of errors.
[ Parent | on HN ]
Re:Go’s march to low-latency GC by arcticbull on Wednesday July 06, 2016 @05:19PM (#12045963)
Yeah, that's exactly what I was trying to say. Rust does all the bookkeeping at compile time, Swift keeps a lot of it at run-time although the compiler can easily optimize away a lot of lifecycle stuff too when it's in scope, so I assume it either does or will.

I agree that Rust likely does not have the be-all answer to automatic memory management, though what I love about it is that they're pushing the boundaries and getting people thinking differently about memory management.

[ Parent | on HN ]
Re:Go’s march to low-latency GC by weberc2 on Thursday July 07, 2016 @12:23PM (#12050312)
> I agree that Rust likely does not have the be-all answer to automatic memory management, though what I love about it is that they're pushing the boundaries and getting people thinking differently about memory management.

Me too. I intend to use it for more of my hobby things, but Go is currently the best fit. Eventually I imagine Rust will pick up some decent GUI libraries or at least get decent editor support (vim-go is lightyears ahead of YCM+racer) and I'll be able to afford to justify using it more.

[ Parent | on HN ]