Add support for the wasm32-unknown-unknown target - #38
Merged
Conversation
`MaybeSend`/`MaybeSync` traits and a conditional `BoxFuture` alias
wasm as well and cleanup
hirrolot
self-requested a review
July 18, 2026 22:19
hirrolot
requested changes
Jul 18, 2026
Contributor
Author
|
I went ahead and wrote a simple macro named |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces
MaybeSend/MaybeSynctraits and a conditionalBoxFuturealias so handler and future bounds relax to nothing onwasm32-unknown-unknownwhile remaining identical to Send/Sync on native targets.This lets
!Sendfutures flow through handlers onwasm32without any unsafe.