You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the build() method of the Instance.Builder() includes a lot of logic to map declared imports to the provided imported values (in particular, see mapHostImports(). This causes some idiosyncrasies such as having a "strange" signature for the main Instance constructor:
publicInstance(
Modulemodule,
Global[] globalInitializers,
intimportedGlobalsOffset, // these offsets should not be really handled at this pointintimportedFunctionsOffset,
intimportedTablesOffset,
Memorymemory,
the mapping between imports of a Module and the provided ImportValues could be handled externally; in particular, in the light of having an externalized "Linking" mechanism, the Linker, might provide a strategy to resolve such mappings.
In the current state, even without a Linker it might be even possible that Store (or a related, new class) could be a better place to handle such a logic.
The text was updated successfully, but these errors were encountered:
the
build()
method of theInstance.Builder()
includes a lot of logic to map declared imports to the provided imported values (in particular, seemapHostImports()
. This causes some idiosyncrasies such as having a "strange" signature for the mainInstance
constructor:the mapping between imports of a
Module
and the providedImportValues
could be handled externally; in particular, in the light of having an externalized "Linking" mechanism, theLinker
, might provide a strategy to resolve such mappings.In the current state, even without a
Linker
it might be even possible thatStore
(or a related, new class) could be a better place to handle such a logic.The text was updated successfully, but these errors were encountered: