-
Notifications
You must be signed in to change notification settings - Fork 155
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
Depends on an outdated and soon-to-be-defunct version of wasmparser #523
Comments
wasm support in this crate hasn't been maintained for a long time. @RReverser Are you still using the wasm support? |
Not in the current project, but I do from time to time. In theory, Wasm support shouldn't require active maintenance, since it's just used as a container for DWARF sections, but bumping the dependency is worthwhile, yeah. |
@RReverser Updating |
It ended up not being too bad to update wasmparser, see #528. |
Hm I don't really remember enough context, it's been years - what do you mean by "go back" or "simple parser"?
Looks great! |
Compilation of gimli examples warns:
This error is in a very very old version of wasmparser, so presumably it has been fixed already, but
object
still has a dev-dependency on the bad old version.The text was updated successfully, but these errors were encountered: