Ryan Levick (rylev) (Oct 06 2023 at 13:44): Ryan Levick (rylev) (Oct 06 2023 at 13:44):@Peter Huene I have the need to compose a component that uses resources, but unfortunately, they're not yet implemented. I'm wondering what your feeling is on the difficulty of adding resource support. I know you're in the middle of a significant rewrite, so I'm unsure if it's worth it for me to onboard to a codebase that will be changing significantly.
Peter Huene (Oct 06 2023 at 16:46):I'm not exactly sure how much work is required to implement it, but I'm still several weeks out from being able to slot in the replacement code, so if this is blocking you, it might be worth investigating
Peter Huene (Oct 06 2023 at 16:46):The replacement will definitely support resources (once I get it to that point)
Ryan Levick (rylev) (Oct 06 2023 at 17:13):I have a temporary work around so if the new version will support resources, it's probably easiest for me to just wait. Thanks though!
fitzgen (he/him) (Oct 06 2023 at 22:25):as a heads up I am doing a pretty large refactor to wasmparser and making there be a type id per kind of type instead of just one big uni-typed TypeId. this has a pretty big effect on a lot of wasm-tools, including wasm-compose so if anyone starts implementing this in wasm-compose give me a heads up please because we will 100% conflict with each other
Joel Dice (Oct 18 2023 at 13:30):I'm interested in making a demo that passes resource handles across component boundaries, which will require at least minimal support for resources in wasm-compose, so I may take a crack at this early next week if nobody else has. @fitzgen (he/him) what's the current state of your wasmparser refactor?
fitzgen (he/him) (Oct 18 2023 at 14:52):It compiles but I’m still working through all the tests on the wasmparser side of things. Don’t let me hold you up if you’ve got the fire in you to start implementing resources support in wasm-compose
Last updated: Dec 23 2024 at 12:05 UTC