hyperlight-dev / hyperlight-dev/hyperlight-wasm
use the #[guest_func] macro on `init_wasm_runtime` instead of manually calling register_function?
Open
Nobody has claimed this yet.
lifecycle/needs review
- Dominant language
- Rust
- Stars
- 728
- Forks
- 39
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 23
Description
Not strictly related to your PR, but can we use the #[guest_func] macro on init_wasm_runtime instead of manually calling register_function?
Originally posted by @ludfjig in https://github.com/hyperlight-dev/hyperlight-wasm/pull/389#discussion_r2849892313
Contributor guide
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 at the init_wasm_runtime entry point and compare its manual register_function call with the existing #[guest_func] macro usage. Confirm the macro can replace the current registration approach without changing runtime behavior, then run the relevant test suite to verify the refactor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100