winmsg-executor 0.3.2

Per-thread async rust executor for windows
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

# `winmsg-executor`


[![Crates.io](https://img.shields.io/crates/v/winmsg-executor)](https://crates.io/crates/winmsg-executor)
![Crates.io License](https://img.shields.io/crates/l/winmsg-executor)
[![docs.rs](https://img.shields.io/docsrs/winmsg-executor)](https://docs.rs/winmsg-executor)

Per-thread async Rust executor for Windows.
Each task is backed by a [message-only window][1].
The executor thread runs the native [Windows message loop][2], which dispatches wake messages to the task's window procedure, which polls the task future.

## Features


- Easy data sharing within a thread because `Send` or `Sync` is not required for the task future.
- Runs multiple tasks on the same thread. Tasks can spawn new tasks and await the result.
- Modal windows like menus do not block other tasks running on the same thread.
- Helper code to implement window procedures with closures that can have state.

## Comparison with similar crates


Both of the listed crates run one task/future per thread and expose only `block_on()`.
[Is block_on an executor?](https://github.com/rust-lang/async-book/issues/219)

### [`windows-executor`](https://github.com/haileys/windows-executor/)


- Polls its future directly from the message loop.
- Does not create a window at all: Wakers store the message loop's thread id and notifies it with `PostThreadMessage()`.
- Does not close the thread's message loop (no `PostQuitMessage()` call) when the task future returns.

### [`windows-async-rs`](https://github.com/saelay/windows-async-rs/)


- Polls directly from the message loop even when receiving broadcast messages unrelated to the task.
- Questionable use of unsafe code

## License


Licensed under either of

- Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or <http://www.apache.org/licenses/LICENSE-2.0>)
- MIT license ([LICENSE-MIT](LICENSE-MIT) or <http://opensource.org/licenses/MIT>)

at your option.

### Contribution


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the
work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

[1]: https://learn.microsoft.com/en-us/windows/win32/winmsg/window-features#message-only-windows
[2]: https://learn.microsoft.com/en-us/windows/win32/winmsg/messages-and-message-queues