elliottt opened PR #6802 from elliottt:trevor/trappable-error-test-multiple-modules
to bytecodealliance:main
:
Add a test for the changes in #6795 to
trappable_error_type
argument of the hostbindgen!
macro. The test uses an error type defined in a different interface as atrappable_error_type
, and verifies that the code generator handles that by lifting those result types intoanyhow::Error
.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
elliottt requested alexcrichton for a review on PR #6802.
elliottt requested wasmtime-core-reviewers for a review on PR #6802.
elliottt requested pchickey for a review on PR #6802.
elliottt edited PR #6802:
Add a test for the changes in #6795 to
trappable_error_type
argument of the hostbindgen!
macro. The test uses an error type defined in a different interface as atrappable_error_type
, and verifies that the code generator handles that by lifting those result types intoanyhow::Error
.The component introduced in this test doesn't make use of multiple modules, and is a complete copy of the component used in the previous
enum_error
test. This works out because of subtyping, but still allows us to test the interface generated by thebindgen!
macro.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton submitted PR review.
alexcrichton merged PR #6802.
Last updated: Nov 22 2024 at 17:03 UTC