Update bitvec requirement from 0.20.1 to 1.0.1

[dependabot]

Updates the requirements on bitvec to permit the latest version.

Changelog

Sourced from bitvec's changelog.

1.0.1

Notes

Performance regressions have been reported between the development series 0.20 onwards and 1.0. It appears at least some of these regressions are due to the removal of the #[inline] attribute on bitvec public functions.

This attribute has been applied to all bitvec functions. You may see regressions in size of your final artifact, but you should also see improvements in your runtime speed. This is being tracked in [sharksforarms/deku#246].

Changes

• The bits![static mut …] invocation has been made unsafe at the invocation site, in response to [Issue #156] filed by GitHub user [@​SimonSapin].

  This is technically an API break (formerly safe code now requires an unsafe block) but as no run-time behavior or compile-time types have changed except for this, and Rust considers breaking incorrect code to be acceptable within SemVer patches, I am publishing it as a patch.

• GitHub user [@​dtolnay] fixed incorrect serde behaviors in [Pull Request #185]. This behavior was first reported in [Issue #167] by GitHub user [@​Nelarius].

• Compilation no longer depends on environment variables set by Cargo, as requested in [Pull Request #162] by GitHub user [@​rocallahan].

• The bitvec![val; len] macro can again take len as a runtime value as well as a compile-time constant. [Pull Request #160] was provided by GitHub user [@​coolreader18].

• The return types of slice::Iter::by_{refs,vals} are restored to named types, rather than impl Iterator... opaque types. This allows them to be used directly in other sites. This defect was reported in [Issue #169] by GitHub user [@​dignifiedquire].

1.0.0

🚨 THIS IS A BREAKING CHANGE RELEASE! 🚨

Your code has broken. You will need to change it in order to use this. This work on your part is worth it.

This release has a great deal of changes from the 0.22 development series! Most breaking changes should have reasonable error messages indicating how they can be repaired.

Removed APIs do not have deprecation notices! Use of removed APIs will fail to

... (truncated)

Commits

• See full diff in compare view

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 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)

[dependabot]

The following labels could not be found: A2-insubstantial, B0-silent, C1-low 📌.