Refactor how InitContext
works with factors
#3134
Open
+201
−158
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.
This commit is a refactoring to replace the concrete
InitContext
structure with a generic type parameter instead. The motivation for this is to prepare for handling bytecodealliance/wasmtime#10770. That's a big change to howadd_to_linker
functions work, notably that the argument to the generated functions is afn
, not aF: Fn
. WASI factors currently rely on the closure-like nature this argument which means it's not compatible with that change. The refactoring to use atrait InitContext
here enables plumbing a type parameter through a function to be able to get a function pointer without relying on closures.