Comments (1)
The following v0.1 example is
use async_executor::{LocalExecutor, Task};
let local_ex = LocalExecutor::new();
local_ex.run(async {
let task = Task::local(async { 1 + 2 });
assert_eq!(task.await, 3);
});
almost equivalent to the following in v1:
use async_executor::LocalExecutor;
use futures_lite::future;
let local_ex = LocalExecutor::new();
future::block_on(local_ex.run(async {
let task = local_ex.spawn(async { 1 + 2 });
assert_eq!(task.await, 3);
}));
If you want a similar API to v0.1, you can use a helper something like this:
use async_executor::LocalExecutor;
let local_ex = LocalExecutor::new();
helper::run_local(async {
let task = helper::spawn_local(async { 1 + 2 });
assert_eq!(task.await, 3);
});
mod helper {
use async_executor::{LocalExecutor, Task};
use scoped_tls::scoped_thread_local;
scoped_thread_local!(static LOCAL_EX: LocalExecutor);
pub fn run_local<T>(local_ex: &LocalExecutor, future: impl std::future::Future<Output = T>) -> T {
LOCAL_EX.set(local_ex, || {
futures_lite::future::block_on(local_ex.run(f))
})
}
pub fn spawn_local<T>(future: impl std::future::Future<Output = T>) -> Task<T> {
if LOCAL_EX.is_set() {
LOCAL_EX.with(|local_ex| local_ex.spawn(future))
} else {
panic!("`spawn_local()` must be called from a `LocalExecutor`")
}
}
}
Note that in 0.1 LocalExecutor::run + Task::local and similar API like above, you can easily write code like can cause a deadlock due to recursive block-on.
refs: a28a964
from async-executor.
Related Issues (20)
- Wake up threads more aggressively if there is known work to do HOT 3
- 1.9.0 may need to be yanked HOT 12
- A leaked Executor does not need to track active tasks HOT 2
- Add hook to be called when new pending task is available HOT 7
- Update to fastrand 2.0.0 isn't published HOT 3
- After non-breaking v1.5.2 release some types suddenly became non-send HOT 4
- Stack overflow when updating from 1.5.1 to 1.5.3 HOT 9
- Panic with version 1.5.3 HOT 1
- open-rmf/rmf_site freezes when updating from 1.5.1 to 1.5.3 HOT 4
- Can you give me an example on how to spawn tasks in a loop but limit total number of tasks? HOT 1
- BorrowError on a server with a huge amount of tasks HOT 2
- Push task directly to the local queue HOT 1
- "Next task" optimization HOT 2
- v1.7 no longer compiles for `wasm32` HOT 6
- Allow creating tasks with metadata
- try_tick considered harmful
- Panic on multithreaded browser Wasm HOT 4
- Efficient way of batch spawning a large number of tasks HOT 3
- MSRV might be set too low HOT 1
- Tick counter can overflow on debug mode
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 async-executor.