Remove component union types#6913
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
c86c020 to
1b7c863
Compare
Subscribe to Label Actioncc @fitzgen, @peterhuene DetailsThis issue or pull request has been labeled: "cranelift", "cranelift:wasm", "fuzzing", "wasmtime:api"Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
6be3b47 to
a3d11f3
Compare
| for ty in types.into_iter_err_on_gc_types() { | ||
| let ty = environ.convert_func_type(&ty?); | ||
| environ.declare_type_func(ty)?; |
| for ty in types.into_iter_err_on_gc_types() { | ||
| let ty = self.convert_func_type(&ty?); | ||
| self.declare_type_func(ty)?; |
|
I just pushed an update here anticipating a wit-bindgen 0.11.0 release. Obviously CI failed, but someone with access can hopefully just retrigger the CI jobs after that release and this should then be mergeable. The previous CI run against wit-bindgen |
|
At this rate I think I'll post a bump for 0.11.0 on Monday, but it'll definitely include this |
|
Oh oops wrong project, I see now! I think it's ok to avoid a wit-bindgen update here as that's mainly used for tests. The dependency between wit-bindgen and wasmtime mainly goes the other direction where wit-bindgen relies on wasmtime for tests, but it's ok in this regard for them to be slightly out of sync. |
|
Ah yeah I didn't really think that through. Well I'll fix it up when I get a chance if someone else doesnt get to it. |
9767ff1 to
fa76ff9
Compare
- Bump wasm-tools deps - Use new TypeSectionReader::into_iter_err_on_gc_types method
|
This should be ready now. |
- Bump wasm-tools deps - Use new TypeSectionReader::into_iter_err_on_gc_types method
...and bump wasm-tools deps.
Fixes #6871