Open
Conversation
a213a74 to
0ee437e
Compare
0ee437e to
476aec3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.2→1.5.0Release Notes
BurntSushi/byteorder (byteorder)
v1.5.0Compare Source
v1.4.3Compare Source
v1.4.2Compare Source
v1.4.1Compare Source
v1.4.0Compare Source
v1.3.4Compare Source
=====
This patch release squashes deprecation warnings for the
try!macro, inaccordance with byteorder's minimum supported Rust version (currently at Rust
1.12.0).
v1.3.3Compare Source
=====
This patch release adds
ByteOrder::write_i8_into()as a simple, safe interfacefor ordinarily unsafe or tedious code.
v1.3.2Compare Source
=====
This patch release adds
ReadBytesExt::read_i8_into()as a simple, safe interfacefor ordinarily unsafe or tedious code.
v1.3.1Compare Source
=====
This minor release performs mostly small internal changes. Going forward, these
are not going to be incorporated into the changelog.
v1.3.0Compare Source
=====
This new minor release now enables
i128support automatically on Rustcompilers that support 128-bit integers. The
i128feature is now a no-op, butcontinues to exist for backward compatibility purposes. The crate continues to
maintain compatibility with Rust 1.12.0.
This release also deprecates the
ByteOrdertrait methodsread_f32_into_uncheckedandread_f64_into_uncheckedin favor ofread_f32_intoandread_f64_into. This was an oversight from the 1.2 releasewhere the corresponding methods on
ReadBytesExtwere deprecated.quickcheckandrandwere bumped to0.8and0.6, respectively.A few small documentation related bugs have been fixed.
v1.2.7Compare Source
=====
This patch release excludes some CI files from the crate release and updates
the license field to use
ORinstead of/.v1.2.6Compare Source
=====
This patch release fixes some test compilation errors introduced by an
over-eager release of 1.2.5.
v1.2.5Compare Source
=====
This patch release fixes some typos in the docs, adds doc tests to methods on
WriteByteExtand bumps the quickcheck dependency to0.7.v1.2.4Compare Source
=====
This patch release adds support for 48-bit integers by adding the following
methods to the
ByteOrdertrait:read_u48,read_i48,write_u48andwrite_i48. Corresponding methods have been added to theReadBytesExtandWriteBytesExttraits as well.v1.2.3Compare Source
=====
This patch release removes the use of
feature(i128_type)from byteorder,since it has been stabilized. We leave byteorder's
i128feature in placein order to continue supporting compilation on older versions of Rust.
v1.2.2Compare Source
=====
This patch release only consists of internal improvements and refactorings.
Notably, this removes all uses of
transmuteand instead uses pointer casts.v1.2.1Compare Source
=====
This patch release removes more unnecessary uses of
unsafethatwere overlooked in the prior
1.2.0release. In particular, theReadBytesExt::read_{f32,f64}_into_checkedmethods have been deprecated andreplaced by more appropriately named
read_{f32,f64}_intomethods.Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.