Releases: smol-rs/async-executor
Releases · smol-rs/async-executor
v1.13.3
27 Aug 01:41
Compare
Sorry, something went wrong.
No results found
Avoid places where the code had a possibility to block or panic. (#147 )
v1.13.2
28 Apr 17:58
Compare
Sorry, something went wrong.
No results found
Fix build failure with minimal-versions. (#132 )
Prevent executor from becoming unusable by panic of the iterator passed by the user to the spawn_many
. (#136 )
Reduce memory footprint. (#137 )
v1.13.1
07 Sep 17:39
Compare
Sorry, something went wrong.
No results found
Fix docs.rs build. (#125 )
v1.13.0
16 Jul 01:37
Compare
Sorry, something went wrong.
No results found
Relax the Send
bound on LocalExecutor::spawn_many
. (#120 )
Ensure all features are documented on docs.rs
. (#122 )
v1.12.0
25 May 19:05
Compare
Sorry, something went wrong.
No results found
Add static executors, which are an optimization over executors that are kept
around forever. (#112 )
v1.11.0
14 Apr 05:53
Compare
Sorry, something went wrong.
No results found
Re-export the async_task::FallibleTask
primitive. (#113 )
Support racy initialization of the executor state. This should allow the executor to be
initialized on web targets without any issues. (#108 )
v1.10.0
07 Apr 15:18
Compare
Sorry, something went wrong.
No results found
Add a function spawn_batch
that allows users to spawn multiple tasks while only locking the executor once. (#92 )
v1.9.1
30 Mar 04:11
Compare
Sorry, something went wrong.
No results found
Remove the thread-local optimization due to the bugs that it introduces. (#106 )
v1.9.0
22 Feb 05:03
Compare
Sorry, something went wrong.
No results found
Re-introduce the thread-local task push optimization to the executor. (#93 )
Bump async-task
to v4.4.0. (#90 )
Replace some unnecessary atomic operations with non-atomic operations. (#94 )
Use weaker atomic orderings for notifications. (#95 )
When spawning a future, avoid looking up the ID to assign to that future twice. (#96 )
v1.8.0
24 Nov 16:22
Compare
Sorry, something went wrong.
No results found
When spawned tasks panic, the panic is caught and then surfaced in the spawned
Task
. Previously, the panic would be surfaced in tick()
or run()
. (#78 )