https://github.com/vorner/coronet
Abusing async-await to get other generator-like functionality
https://github.com/vorner/coronet
Last synced: 11 months ago
JSON representation
Abusing async-await to get other generator-like functionality
- Host: GitHub
- URL: https://github.com/vorner/coronet
- Owner: vorner
- License: apache-2.0
- Created: 2021-12-12T19:15:57.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2021-12-12T19:37:44.000Z (over 4 years ago)
- Last Synced: 2025-07-25T11:43:09.239Z (12 months ago)
- Language: Rust
- Size: 15.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE-APACHE
Awesome Lists containing this project
README
# Coronet
Assorted coroutine utilities, abusing Rust async/await under the hood.
Rust has generators as an unstable feature. They would allow writing iterators,
parsers, and many other such things conveniently, but hey, they are unstable and
likely to change.
But they are also used internally by the compiler to create async functions.
Could the async functions be abused to give us the generators superpowers?
For now, this crate is somewhat *experimental*. Expect rough edges, weird error
messages, things changing between releases and such (but I intend to minimize
the use of `unsafe` and stick to things that I believe to work correctly once
they compile).