Eric Holk

Oh sorry, I misspoke! I meant to ask whether we need `Future` and `IntoFuture` in the prelude, not the standard library. I'll edit my comment.

> > Most people don't implement Future directly > > Yeah, but I would assume more people using them as impl traits in return or arg position, like `fn x()...

It's possible that once we have `AsyncIterator` we may see `Future` used a lot more too, depending on how the API shapes up.

@rfcbot merge Assuming I can work rfcbot correctly, I'm going to go ahead and add checkboxes so we can get the ball rolling. It looks like there's a fairly tight...

At the most recent CG meeting, we had some opposition to the idea of requiring custom sections to be at the end. The reason is that some uses cases for...

One idea I had was to add an additional trait, something like this: ```rust trait SchedulingWeight { fn scheduling_weight(&self) -> usize; } ``` Then for tuples we'd have something like:...

Adding something like `priority_hint` to the `Future` trait seems pretty similar to the `size_hint` method on `Iterator`: https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.size_hint

I think an experiment seems like a good idea. I wonder if we could do it as a separate crate to prove the idea and then use that as evidence...

One thing holding this back right now is needing static mutexes. It looks like some OpenCL implementations do not properly handle multiple calls into the API, so we use a...

I just started a branch that compiles on stable Rust: https://github.com/eholk/rust-opencl/tree/rust-stable I removed the platform lock, so we'll need some testing and experimentation to see if that was safe. Also,...