News for hackers. Stuff that matters.
Re:This Week in Rust – Static linking, Win64 by steveklabnik on Sunday December 01, 2013 @08:11PM (#6830510)
Rust doesnt really offer GC, the @pointers are more like ARC with cycle detection, and are behind a featre flag now.

Rust is talking about getting read of N:M threading and returning to 1:1, I'm not 100% sure that's landed or was fully decided yet.

That said, this is a great description.

Re:This Week in Rust – Static linking, Win64 by eridius on Sunday December 01, 2013 @08:15PM (#6830528)
@-pointers, right now, are retain-counted. But that's just a temporary implementation detail. The current direction is to remove @-pointers entirely and implement both retain-counting and true garbage collection in the standard libraries.

And getting rid of N:M threading and returning to 1:1 seems rather unlikely to happen. More likely is simply work to ensure that Rust can run well under both N:M and 1:1 threading models.

Re:This Week in Rust – Static linking, Win64 by dbaupp on Sunday December 01, 2013 @08:16PM (#6830535)
I think the core team have decided to attempt to offer first class M:N and 1:1 support, so that one has a choice.
Re:This Week in Rust – Static linking, Win64 by bascule on Sunday December 01, 2013 @08:18PM (#6830546)
They're actually talking about pursuing a "N:1" concurrency model (i.e. userland-managed coroutines in the kernel). See: https://www.youtube.com/watch?v=KXuZi9aeGTw
Re:This Week in Rust – Static linking, Win64 by bjz_ on Monday December 02, 2013 @12:53AM (#6831973)
> Rust doesnt really offer GC, the @pointers are more like ARC with cycle detection, and are behind a featre flag now.

@ is being removed, but GC will still be there - implemented properly as a library with language hooks (via traits) to make it nice and safe to work with. You will be able to create your own memory management strategies using those traits.

Re:This Week in Rust – Static linking, Win64 by portmanteaufu on Sunday December 01, 2013 @08:27PM (#6830593)
Last I had heard they were going to try and provide both M:N and 1:1 implementations and using whichever was more appropriate for the platform. I could be wrong about that, though, it's a hazy memory from a lengthy mailing list discussion.