News for hackers. Stuff that matters.
Re:Ruby 3.0 and the new FiberScheduler interface by tinco on Tuesday December 29, 2020 @08:02PM (#25577095)
Does this mean that Rust's Future trait is incorrectly named? Or at least not named according to the academic use of the word?

Of course because Rust's runtime or lack thereof aims to be zero overhead a Future could never be without the poll function.. right? You need a runtime to make regular functions accept these magic opaque future values.

Re:Ruby 3.0 and the new FiberScheduler interface by chrisseaton on Wednesday December 30, 2020 @07:37AM (#25581141)
Yes not named according to the original paper.

Yes it requires some kind of special compiler or runtime support.