-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
fix(demangle): Update cpp_demangle due to breaking change #244
fix(demangle): Update cpp_demangle due to breaking change #244
Conversation
cpp_demangle::DemangleOptions now has a no_return_type field which causes an issue in symbolic-demangle lib.rs the breaking change occured in a patch version which means running `cargo update` breaks people's builds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well this is unfortunate
Would it be possible to merge & make a new release asap please ? |
In case it helps anyone stumbling on it before a new release is out, a workaround in the meantime is to pin cpp_demangle in a Cargo.toml file, for example: symbolic-demangle = "6.1"
cpp_demangle = "=0.2.16" |
👍 I'll bump and release. This will take a little bit this time. Next time something like this happens, I think the "right" course of action would be to ask maintainers to yank the offending version and bump properly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with the TODO comment. There's also #165 still open. I think the proper enhancement will be to add many more generalized flags to DemangleOptions
and convert it into a builder to not break.
Oh indeed, I'll do just that next time, thanks for your time! |
Thanks for reporting this to me btw. |
Fixes #243
cpp_demangle::DemangleOptions now has a no_return_type field which causes an issue in symbolic-demangle lib.rs
the breaking change occured in a patch version which means running
cargo update
breaks people's builds.