-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
enum cases size is out of bounds #1019
enum cases size is out of bounds #1019
Comments
PS: the wit works as expected on the host side. |
Increase some limits from 1_000 to 10_000 to handle bytecodealliance/wit-bindgen#1019
Increase some limits from 1_000 to 10_000 to handle bytecodealliance/wit-bindgen#1019
Thanks for the report! The limit here should be fixed in bytecodealliance/wasm-tools#1713 |
@alexcrichton good stuff, thanks for hopping on this so quick! I just got started with the |
* Increase limits of some component types Increase some limits from 1_000 to 10_000 to handle bytecodealliance/wit-bindgen#1019 * Lower flags limit
any idea when this is making it in a release? I tried pulling in the git version of |
The validation error was fixed in a relatively deep portion of the stack but that was awhile ago and so the update should have percolated by now. @MatthiasGrandl could you detail a bit more how you're seeing this error? That'll help pinpoint what missed the update and what should get updated. |
It happens during compilation of a rust wasm component with |
Ah I think you're running into |
Bump crates to their latest, notably which I think will help resolve bytecodealliance/wit-bindgen#1019.
Ok a new wit-bindgen is released and bytecodealliance/cargo-component#335 should update cargo-component. Mind trying again with a git version of cargo-component to confirm the issue is resolved once that merges? |
Bump crates to their latest, notably which I think will help resolve bytecodealliance/wit-bindgen#1019.
I generated a very large enum (it's the icon set https://lucide.dev/icons/) . So I have 1424 cases, but sadly it breaks with
wit-bindgen
with the following error:I tried using a
variant
instead, but same error. So is this expected or a bug? Is there a suggested alternative for my usecase of exposing a typesafe icon set to my webassembly components?The text was updated successfully, but these errors were encountered: