2 ms·
So, Futures are moving into the standard library; there’s been a last minute procedural issue over one name, and then they’ll be in. So “futures 1.0” isn’t as i
by steveklabnik 8y ago
So, Futures are moving into the standard library; there’s been a last minute procedural issue over one name, and then they’ll be in. So “futures 1.0” isn’t as important, the futures library mostly provides extra utilities, not the core of futures themselves. It’s likely this means they’ll be in 1.33, February 28 (if my math is right)
- Matthias247 8y ago> So, Futures are moving into the standard library; there’s been a last minute procedural issue over one name, and then they’ll be in. That's just the open issue around pinning. There are however a few open discussions around the futures/task/waker parts, from the other RFC. I just wrote down a list of the open points here: https://github.com/aturon/rfcs/pull/15#issuecomment-445492382 https://github.com/aturon/rfcs/pull/15#issuecomment-44549238...
- steveklabnik 8y agoOh right, I forgot about that but, thank you!