Skip to content

Add wasm32 support to the rust sdk (updated)#4089

Open
kistz wants to merge 21 commits intoclockworklabs:masterfrom
kistz:rust-web-sdk-updated
Open

Add wasm32 support to the rust sdk (updated)#4089
kistz wants to merge 21 commits intoclockworklabs:masterfrom
kistz:rust-web-sdk-updated

Conversation

@kistz
Copy link
Contributor

@kistz kistz commented Jan 21, 2026

Description of Changes

Superscedes and is: #2704 so all credit goes to @thlsrms

This branch is updates to the latest master through cherry-picking leaving out the problematic switch to anymap3 thats currently holding back the pr.
All commit authorships are kept since i only rebased it :>
Since @thlsrms seems to be unavailbale right now i'd say we push this to finish line @gefjon ?

Testing

thlsrms and others added 20 commits January 21, 2026 19:51
- `DbConnectionBuilder::build` becomes async without tokio's
block_in_place.

Still need to add `web` feature flag.
Renamed the `run_threaded` method on `wasm32` to better reflect its
behavior of spawning a background task.

The generated `DbConnection` methods `run_threaded`, `run_background`,
and `advance_one_message_blocking` now include runtime panics with a
clear error feedback when called on unsupported targets.
Trim down repetitive `cfg` clauses by extracting common lock patterns
into `get_lock_[sync|async]`.
Moves the creation of DbContextImplInner and DbContextImpl into private
helper functions (`build_db_ctx_inner` and `build_db_ctx`) to reduce
duplication between the web and non-web implementations of `build_impl`.
@jazzay
Copy link

jazzay commented Feb 24, 2026

I've been hoping #2704 would land a while ago, so if we could get this one across the line and into the 2.0.x release soon that would be much appreciated.

@kistz
Copy link
Contributor Author

kistz commented Feb 25, 2026

@jazzay its curerntly waiting on the ci which @bfops was experimenting with at some point.
Maybe he can chime in if its still on his radar/roadmap :>
(oh sry i was he already responded on another pr #4319 so maybe if i already pinged, you can answer whats your prefered strategy is for bringing this in? should i try to update my pr or close it in favor of the ai iuntested pr? im not super invested in this so i dont mind either way :> )

@bfops
Copy link
Collaborator

bfops commented Feb 26, 2026

@jazzay its curerntly waiting on the ci which @bfops was experimenting with at some point. Maybe he can chime in if its still on his radar/roadmap :> (oh sry i was he already responded on another pr #4319 so maybe if i already pinged, you can answer whats your prefered strategy is for bringing this in? should i try to update my pr or close it in favor of the ai iuntested pr? im not super invested in this so i dont mind either way :> )

Good question. I still trust humans more than I do AI so if you think you're able to get it updated with latest master, I would appreciate that! Otherwise we can work with the other PR, I'm sure it's at least somewhat close.

Signed-off-by: Zeke Foppa <196249+bfops@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants