Experiment with wasm support #103
Closed
Conversation
This file contains 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
durch
force-pushed
the
wasm-support
branch
2 times, most recently
from
10a4c06
to
f484e63
Compare
|
I'm not able to use the "wasm" feature in 0.27.0. Was it merged? I also tried the 23 beta version, but I'm getting errors because aws-creds tries to use reqwest blocking. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #102
Mostly done with clunky feature gates for now. This branch is published to
crates.ioasv0.23.0-beta3. Functionality is feature gated, for wasm there is awasmfeature that leaves inblockingfamily ofBucketmethods,default-featuresneed to be disabled.