Update bitvec requirement from 0.16 to 0.17

[dependabot-preview[bot]]

Updates the requirements on bitvec to permit the latest version.

Changelog

Sourced from bitvec's changelog.

0.17.0

Added

• BitField trait now has {load,store}_{le,be} methods for explicitly choosing element order when performing storage. The load/store methods default to the target’s byte endiannes as a convenience. These may be deprecated in the future, if the explicit choice is strongly preferred.

  See the module and trait documentation for more detail.

• GitHub user [@mystor] provided a bits! macro in [Pull Request #34] which enables compile-time construction of &'static BitSlice<O, T> regions. This macro is currently limited to working with the literal BitOrder implementator names Local, Lsb0, and Msb0. This is a restriction in the Rust language (identifiers are not yet associated with types during macro expansion), and bitvec does not promise to expand support to other names or types in the future.

• usize implements BitStore, and is now the default type argument.

Changed

• Rename the cursor module to order, the Cursor trait to BitOrder, and the BigEndian and LittleEndian types to Msb0 and Lsb0, respectively
• Fold BitsMut into Bits

Removed

• The Rust types T, [T; 0 <= N <= 32], and [T] for T: BitStore no longer implement AsRef<BitSlice<_, T>> or AsMut<BitSlice<_, T>>. This decision was made due to consideration of [Issue #35], by GitHub user [@Fotosmile].

• The store::Word type alias is removed, as it was a patch for usize’s absence as a BitStore type. All uses of the Word alias can be replaced with usize without issue.

0.16.2

Fixed

Updated radium dependency to 0.3, which enables it to compile on the thumbv7m-none-eabi target. This addresses [Issue #36], which noted that bitvec failed to compile for that target due to reduced support for atomic types in core. Thanks to GitHub user [@lynaghk] for the report.

0.16.1

This is a hotfix for [Issue #33], filed by GitHub user [@jonas-schievink]. BitVec::reserve computed an incorrect element count to pass to Vec::reserve,

... (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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[sunjay]

@myrrlyn can you update the bits example for the latest bitvec?

[myrrlyn]

Is it going to do this every time I release a 0.x version, and is there a way to make it not do that?

Though this is social pressure to stabilize a 1.0 soon, so, who can say if it's bad or not

[sunjay]

It's going to do this every time a new version of bitvec is released. I just figure that's probably a good idea if we keep the example up to date. You have the best understanding of the example and of bitvec, so I pinged you. You can probably update it pretty quickly given that you know what's changed. :)

[myrrlyn]

If you assign me, does that give me push permission to this branch?

[sunjay]

I don't think so, but I know that if you open a PR that updates the dependency on master, this PR will automatically be closed once that change is merged.

[dependabot-preview[bot]]

A newer version of bitvec exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.