pasts
pasts copied to clipboard
ardaku
Minimal and simpler alternative to the futures crate.
And figure out a way to not run futures in `Drop`.
~https://github.com/rust-lang/rust/issues/93178 (remove pin-utils dependency when **`no-std`** is enabled)~ - [ ] https://github.com/rust-lang/rust/issues/86918 (remove `Unpin` requirement for `Notifier` impl on `Pin`)
Supports compiling pasts to no-std on stable with a feature flag to pull in faux_alloc. This removes the need for all the nightly boilerplate. Closes https://github.com/ardaku/pasts/issues/18
When creating the `Executor`, it should be possible to set a limit on the number of spawned tasks to avoid allocation. Setting the limit to zero should fallback to using...
Because we have [`Arc::from`](https://doc.rust-lang.org/std/sync/struct.Arc.html#impl-From%3CT%3E), [Executor::new()](https://docs.rs/pasts/0.11.0/pasts/struct.Executor.html#method.new) can take `Into Arc`, and pass an `Arc` created outside the global allocator in the no-std example.
I no longer think the benefits of having `Notify` as a separate trait are worth the trade-off, since in practice, most `Notify`s have a point where they could end. Additionally,...
**Describe the bug** Never increments the "current" value, therefore isn't actually fair.
This could possibly work with a homogeneous array with a generic, rather than forcing the use of trait objects (and still support trait objects).
This could be an issue when extending pasts to allow spawning in a thread pool.