Wasm compatibility #64
Closed
Conversation
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
Sosthene00
force-pushed
the
wasm_compatibility
branch
from
ee30dfd to
81b1ec0
Compare
Collaborator
Author
|
Big refactoring today, still missing some implementations and testing in both native and wasm context |
* Abstraction of SpScanner into a trait * Gating of the code with wasm32 target when necessary
Sosthene00
force-pushed
the
wasm_compatibility
branch
from
5c179fb to
d1598be
Compare
Collaborator
Author
|
Closed and replaced by #66 |
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.
A working branch with all the modifications needed to use sp_client in a wasm (browser) context