wasm-futures-executor
pasts
| wasm-futures-executor | pasts | |
|---|---|---|
| 3 | 6 | |
| 29 | 110 | |
| - | 4.5% | |
| 0.0 | 4.0 | |
| almost 2 years ago | 11 months ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wasm-futures-executor
-
How to enable Bulk Memory Operations when compiling to WebAssembly?
RUSTFLAGS='-C target-feature=+bulk-memory' should work according to the readme of https://github.com/wngr/wasm-futures-executor
-
Threading for WASM target
I recommend using it through the wasm-futures-executor crate: https://github.com/wngr/wasm-futures-executor.
-
Web Crypto API
By the way, I built something similar (?): A Rust library that mimics the API of the `futures-executor` crate, but each worker thread is a single WebWorker.
https://github.com/wngr/wasm-futures-executor
pasts
-
`alternator` gives an async function access to data but gives it back on await points
This was one of the original ideas behind pasts. I wanted to share data on a single threaded executor without using RefCell, so I created the Join struct api (renamed and redesigned many times). I'm curious what you think of that approach.
-
Pasts - A No-Std Compatible Async Runtime
Pointing out that you're comparing apples to oranges. First off, that example isn't marked #[no_std], that means it will not work on no-std. It's not the same example. You need to define a panic handler, eh_personality and an allocator all of which are conviniently ignored in your linked example because it targets std instead of no-std. If you look at the actual equivalent example in pasts, it is actually not more boilerplate: https://github.com/ardaku/pasts/blob/stable/examples/timer.rs
What are some alternatives?
wireworld-player - A multithreaded web app for loading and simulating instances of the Wireworld cellular automaton
tarpc - An RPC framework for Rust with a focus on ease of use.
yew - Rust / Wasm framework for creating reliable and efficient web applications
ghost-collections - Safe collections written in stable Rust, based on GhostCell and StaticRc.
worktank - A simple isomorphic library for executing functions inside WebWorkers or Node Threads pools.
async-graphql - A GraphQL server library implemented in Rust
worktank-loader - WebPack plugin for WorkTank which enables you to execute whole files in a worker pool, transparently.
rust - Empowering everyone to build reliable and efficient software.
objectbuffer - JavaScript Object like api, backed by an arraybuffer
rust-rdkafka - A fully asynchronous, futures-based Kafka client library for Rust based on librdkafka
comlink - Comlink makes WebWorkers enjoyable.
smol - A small and fast async runtime for Rust