You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a minimal reproducible example with the patch I got compiling at least - note the diff is inverted so I needed the opposite change from the PR to compile: nuke-web3/cargo-component-workspace-bindings#1 . Although I am not sure that this is the right fix, just what hacked together seems to fix cargo's complaints 😅 .
The patch here is to be more explicit in imports and a long standing weirdness of macro resolution: rust-lang/rust#57966
The text was updated successfully, but these errors were encountered:
nuke-web3
changed the title
Cargo workspaces core and alloc imports and macro exports cannot be resolved
Cargo workspaces core, alloc imports and macro exports cannot be resolved
Mar 18, 2024
It seems that composing a project with a structure like below has resolution issues that need a patch to the bindings generated to function:
Here is a minimal reproducible example with the patch I got compiling at least - note the diff is inverted so I needed the opposite change from the PR to compile: nuke-web3/cargo-component-workspace-bindings#1 . Although I am not sure that this is the right fix, just what hacked together seems to fix cargo's complaints 😅 .
Perhaps this issue would need to be transferred to https://github.com/bytecodealliance/wit-bindgen if the fix should not exist here.
The text was updated successfully, but these errors were encountered: