gwsystems / gwsystems/sledge-serverless-framework
Document and validate that aWSM generated *.bc is a WASI module
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 124
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
aWsm has added support for modules outside of the WASI spec. For example, modules that do not use the linear memory. However, SLEdge seems to be more opinionated around WASI, and it is unclear to me if supporting non-WASI WebAssembly targets has any particular value.
Our documentation should clarify our assumptions around WASI symbols. We should also validate these symbols during dlopen at runtime startup.
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
Start by tracing how aWsm-generated .bc modules reach dlopen during runtime startup and identify the WASI symbols SLEdge assumes. Document those assumptions, add validation for the symbols at startup, and verify behavior for WASI and non-WASI WebAssembly modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, wasm
- Domain
- backend, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100