News for hackers. Stuff that matters.
Re:Announcing Rust 1.20 by steveklabnik on Thursday August 31, 2017 @07:26PM (#15144879)
This is pretty accurate; however, a very long time ago there was a tracing GC!
Re:Announcing Rust 1.20 by iopq on Thursday August 31, 2017 @08:15PM (#15145149)
Are you sure? I thought @ was reference counted in 0.6 and then removed after. Was it before that?
Re:Announcing Rust 1.20 by steveklabnik on Thursday August 31, 2017 @08:29PM (#15145219)
I don't have any citation beyond "Graydon told me one time". It was like, very very long ago, possibly before @T even existed.
Re:Announcing Rust 1.20 by Rusky on Thursday August 31, 2017 @10:09PM (#15145612)
IIRC it was a mark and sweep GC in the OCaml implementation.
Re:Announcing Rust 1.20 by steveklabnik on Thursday August 31, 2017 @11:11PM (#15145830)
That sounds about right.
Re:Announcing Rust 1.20 by jacobush on Friday September 01, 2017 @03:27AM (#15146775)
Wow, I can't believe I have been reading up lately on official Rust documentation and still I was under the impression that Rust had optional GC. Thanks for sorting me out...
Re:Announcing Rust 1.20 by kbenson on Friday September 01, 2017 @08:21PM (#15153380)
Well, I think is sort of does when you use the Rc types, right? It's just much more explicit than a type modifier, it's a type wrapper that requires requires some level of additional code ornamentation in some instances when using later as well. It's just not really any different than using a library in C++ that offers the same, except that in Rust's case the library is part of the stdlib.