embassy/embassy-executor/src/raw/waker_turbo.rs, branch main Unnamed repository; edit this file 'description' to name the repository. executor: Add fallible from_waker getter 2025-12-18T08:57:52+00:00 Dániel Buga bugadani@gmail.com 2025-12-18T08:57:52+00:00 e62adea1f93f8eaba2f9da5ebe90e5f23a480101 






Rustfmt for edition 2024.
2025-10-06T21:19:53+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2025-10-06T20:56:31+00:00

8730a013c395cf0bf4c2fa8eeb7f138288103039












Edition 2024.
2025-10-06T21:19:53+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2025-10-06T20:55:38+00:00

abc8e450f936567ad42cb34b5d2a7941b206aa5d












executor,sync: add support for turbo-wakers.
2023-03-30T15:55:55+00:00

Dario Nieuwenhuis
dirbaio@dirbaio.net

2023-03-30T15:55:55+00:00

80972f1e0e6b6d409cc4d86202608c22e5ee3e5a

This is a `core` patch to make wakers 1 word (the task pointer) instead of 2 (task pointer + vtable). It allows having the "waker optimization" we had a while back on `WakerRegistration/AtomicWaker`, but EVERYWHERE, without patching all crates.

Advantages:
- Less memory usage.
- Faster.
- `AtomicWaker` can actually use atomics to load/store the waker, No critical section needed.
- No `dyn` call, which means `cargo-call-stack` can now see through wakes.

Disadvantages:
- You have to patch `core`...
- Breaks all executors and other things that create wakers, unless they opt in to using the new `from_ptr` API.

How to use:

- Run this shell script to patch `core`. https://gist.github.com/Dirbaio/c67da7cf318515181539122c9d32b395
- Enable `build-std`
- Enable `build-std-features = core/turbowakers`
- Enable feature `turbowakers` in `embassy-executor`, `embassy-sync`.
- Make sure you have no other crate creating wakers other than `embassy-executor`. These will panic at runtime.

Note that the patched `core` is equivalent to the unpached one when the `turbowakers` feature is not enabled, so it should be fine to leave it there.





This is a `core` patch to make wakers 1 word (the task pointer) instead of 2 (task pointer + vtable). It allows having the "waker optimization" we had a while back on `WakerRegistration/AtomicWaker`, but EVERYWHERE, without patching all crates.

Advantages:
- Less memory usage.
- Faster.
- `AtomicWaker` can actually use atomics to load/store the waker, No critical section needed.
- No `dyn` call, which means `cargo-call-stack` can now see through wakes.

Disadvantages:
- You have to patch `core`...
- Breaks all executors and other things that create wakers, unless they opt in to using the new `from_ptr` API.

How to use:

- Run this shell script to patch `core`. https://gist.github.com/Dirbaio/c67da7cf318515181539122c9d32b395
- Enable `build-std`
- Enable `build-std-features = core/turbowakers`
- Enable feature `turbowakers` in `embassy-executor`, `embassy-sync`.
- Make sure you have no other crate creating wakers other than `embassy-executor`. These will panic at runtime.

Note that the patched `core` is equivalent to the unpached one when the `turbowakers` feature is not enabled, so it should be fine to leave it there.