News for hackers. Stuff that matters.
Re:The Piston image library is now pure Rust by steveklabnik on Sunday January 08, 2017 @10:20AM (#13349996)
> as best I remember the history of Rust

There's an RFC for that! https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... (A reminder that this was written in 2014, so statements are about Rust at that time period)

> I think Rust will eventually move back in that direction

Note that tokio is not "green threads" as they're conventionally thought of, though they are similar if you squint, kinda.

Re:The Piston image library is now pure Rust by ekidd on Sunday January 08, 2017 @10:26AM (#13350032)
> Note that tokio is not "green threads" as they're conventionally thought of, though they are similar if you squint, kinda.

Well, I'm leaping ahead to the end of the story, here, and speaking far too loosely about technical details. ;-) Futures + tokio + a possible future async/await proposal would provide a reasonable enough syntax for actors/coroutines in Rust, I suspect.

Re:The Piston image library is now pure Rust by steveklabnik on Sunday January 08, 2017 @10:27AM (#13350045)
Re:The Piston image library is now pure Rust by GolDDranks on Sunday January 08, 2017 @11:05AM (#13350293)
From the author of the mioco coroutine library, there is a new attempt to implement coroutines on top of tokio: https://github.com/dpc/tokio-fiber/ (still under construction, it seems)