Wasmtime GitHub notifications bot (Jun 28 2023 at 22:44): Wasmtime GitHub notifications bot (Jun 28 2023 at 22:44):github-actions[bot] commented on issue #6667:
Subscribe to Label Action
cc @peterhuene
<details>
This issue or pull request has been labeled: "wasmtime:api"Thus the following users have been cc'd because of the following labels:
- peterhuene: wasmtime:api
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
Wasmtime GitHub notifications bot (Jun 28 2023 at 22:51):alexcrichton commented on issue #6667:
This theoretically opens up the door to fancier handling of types in the future as well. For example if a host declares that a record has field
athen fieldbit's currently incompatible with a component that says it has fieldbthen fielda, even if the types of the fields are the same. Threading through this type information could be the start of a basis for resolving this in the future where now all the type information is locally available to build these maps.Now that being said I don't think it's a good idea to do that at this time. The naive implementation would not be very fast and could run a risk of severly slowing down lifting/lowering even more, and it's not really required yet due to everything being generated from
*.witfiles which serve as a source of truth (including field order for example). Perhaps worth mentioning if anyone's curious though.
Last updated: Nov 22 2024 at 17:03 UTC