clockworklabs / clockworklabs/SpacetimeDB
Add support for Wasm memory64
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
https://github.com/bytecodealliance/wasmtime/pull/3153
https://discordapp.com/channels/1037340874172014652/1138585892857057421/1362288225250709525
Also I want to also put out the request for wasm64 support if it's not already on the roadmap. Just spent a few hours working on (the start of) golang support with @Huijiro and apparently golang doesn't support wasm32 currently (it's in development, but it seems like they're stalling on it due to other higher priorities.) Even if it's still limited to 4GB in the end, I just think it would be nice to not have to do weird pointer casts to int32 just to pass the data back to spacetimedb. I might try and implement it at some point myself, but I don't want to make any promises yet, I already have a lot on my plate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are named. Start by reviewing the linked Wasmtime pull request and Discord discussion, then determine the scope of Wasm memory64 support in SpacetimeDB; done means the agreed support is implemented and validated by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100