Comments (4)
This code in the compiler calls it "Unresumed":
https://cs.github.com/rust-lang/rust/blob/0aaad9e757207657064d70bf9e6c1e6eb327bf15/compiler/rustc_middle/src/ty/sty.rs#L487
from futures-concurrency.
NotStarted
sounds like a better name to me though.
from futures-concurrency.
Do we know for sure that a future has never been polled yet?
from futures-concurrency.
Do we know for sure that a future has never been polled yet?
We can't guarantee that, no. Futures would individually have to track whether they've been started or not. Unpin
futures could theoretically be polled once, moved out of their Pin
container, moved into a concurrency operator, and then polled. There's nothing preventing that from happening.
But I think NotStarted
should be viewed from the perspective of the concurrency future: it has not yet started polling it, and in order to guarantee it starts it has to, at least once, loop over each future and hand it a waker.
from futures-concurrency.
Related Issues (20)
- How should I factor my specific problem, and more broadly, how should I handle `Result<!, E>`? HOT 2
- Using .join() on an empty Vec stalls HOT 2
- `TryJoin` on tuple trying to free a null pointer HOT 8
- wrapping_rem called with a value of zero HOT 4
- Handling control flow HOT 2
- Use `Waker::clone_from` internally
- Update traits to use AFITs / associated `impl Future` HOT 1
- `Stream::merge` may be susceptible to stream "barbara battles buffered streams" HOT 3
- Implement precise waking on `alloc` targets HOT 2
- Implement better capacity in our group structures HOT 2
- Forgetten `todo!()` in `try_for_each` impl
- fix perf issues in group structures HOT 1
- Add an inherent into_stream method for ConcurrentIterator
- Declare minimum support rust version in Cargo manifest HOT 1
- ConcurrentStream usage with tokio leads to ACCESS_VIOLATION HOT 4
- no progress with concurrent streams and tokio HOT 1
- [FEATURE] more combinators HOT 3
- Only a single cpu core is utilized when `join`-ing on `tokio` runtime HOT 8
- Fix pin violation in `FutureGroup` HOT 1
- Poor performance when polling futures in random order
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from futures-concurrency.