Skip to content
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

Bump cpp_demangle from 0.3.5 to 0.4.3 #732

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 21, 2023

Bumps cpp_demangle from 0.3.5 to 0.4.3.

Changelog

Sourced from cpp_demangle's changelog.

0.4.3

Released 2023/8/18

Fixed


0.4.2

Released 2023/6/26

Fixed

  • Handling of recursion depth errors has been improved. Exceeding cpp_demangle's recursion limits will now return immediately, which significantly improves performance when attempting to demangle these symbols, and removes the possibility of returning an incorrect demangling if any productions in the symbol might be ambiguous. (#284)[https://redirect.github.com/When parsing, don't swallow recursion depth errors. gimli-rs/cpp_demangle#284]

0.4.1

Released 2023/4/13

Fixed


0.4.0

Released 2022/10/20

Removed

  • The deprecated nightly and cppfilt features are gone.

Changed

  • If no-default-features is used the alloc feature must be explicitly specified.

... (truncated)

Commits
  • bfd256c Release 0.4.3.
  • ad09699 Remove Travis CI and Coveralls
  • 963883e Allow inheriting constructor types to be substitution candidates.
  • 04954c0 Release 0.4.2.
  • 751b06b Fix changelog order.
  • d75415a When parsing, don't swallow recursion depth errors.
  • f76900b Update afl requirement from 0.12.0 to 0.13.1
  • 778433c Release 0.4.1.
  • 00682a3 Add a test for a U/Ul ambiguity that resulted in pathological behavior.
  • 224df6f Reorder parsing of type qualifiers to match the spec.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [cpp_demangle](https://github.com/gimli-rs/cpp_demangle) from 0.3.5 to 0.4.3.
- [Changelog](https://github.com/gimli-rs/cpp_demangle/blob/master/CHANGELOG.md)
- [Commits](gimli-rs/cpp_demangle@0.3.5...0.4.3)

---
updated-dependencies:
- dependency-name: cpp_demangle
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants