11.3.0
2=====
3This new minor release now enables `i128` support automatically on Rust
4compilers that support 128-bit integers. The `i128` feature is now a no-op, but
5continues to exist for backward compatibility purposes. The crate continues to
6maintain compatibility with Rust 1.12.0.
7
8This release also deprecates the `ByteOrder` trait methods
9`read_f32_into_unchecked` and `read_f64_into_unchecked` in favor of
10`read_f32_into` and `read_f64_into`. This was an oversight from the 1.2 release
11where the corresponding methods on `ReadBytesExt` were deprecated.
12
13`quickcheck` and `rand` were bumped to `0.8` and `0.6`, respectively.
14
15A few small documentation related bugs have been fixed.
16
17
181.2.7
19=====
20This patch release excludes some CI files from the crate release and updates
21the license field to use `OR` instead of `/`.
22
23
241.2.6
25=====
26This patch release fixes some test compilation errors introduced by an
27over-eager release of 1.2.5.
28
29
301.2.5
31=====
32This patch release fixes some typos in the docs, adds doc tests to methods on
33`WriteByteExt` and bumps the quickcheck dependency to `0.7`.
34
35
361.2.4
37=====
38This patch release adds support for 48-bit integers by adding the following
39methods to the `ByteOrder` trait: `read_u48`, `read_i48`, `write_u48` and
40`write_i48`. Corresponding methods have been added to the `ReadBytesExt` and
41`WriteBytesExt` traits as well.
42
43
441.2.3
45=====
46This patch release removes the use of `feature(i128_type)` from byteorder,
47since it has been stabilized. We leave byteorder's `i128` feature in place
48in order to continue supporting compilation on older versions of Rust.
49
50
511.2.2
52=====
53This patch release only consists of internal improvements and refactorings.
54Notably, this removes all uses of `transmute` and instead uses pointer casts.
55
56
571.2.1
58=====
59This patch release removes more unnecessary uses of `unsafe` that
60were overlooked in the prior `1.2.0` release. In particular, the
61`ReadBytesExt::read_{f32,f64}_into_checked` methods have been deprecated and
62replaced by more appropriately named `read_{f32,f64}_into` methods.
63
64
651.2.0
66=====
67The most prominent change in this release of `byteorder` is the removal of
68unnecessary signaling NaN masking, and in turn, the `unsafe` annotations
69associated with methods that didn't do masking. See
70[#103](https://github.com/BurntSushi/byteorder/issues/103)
71for more details.
72
73* [BUG #102](https://github.com/BurntSushi/byteorder/issues/102):
74  Fix big endian tests.
75* [BUG #103](https://github.com/BurntSushi/byteorder/issues/103):
76  Remove sNaN masking.
77
78
791.1.0
80=====
81This release of `byteorder` features a number of fixes and improvements, mostly
82as a result of the
83[Litz Blitz evaluation](https://public.etherpad-mozilla.org/p/rust-crate-eval-byteorder).
84
85Feature enhancements:
86
87* [FEATURE #63](https://github.com/BurntSushi/byteorder/issues/63):
88  Add methods for reading/writing slices of numbers for a specific
89  endianness.
90* [FEATURE #65](https://github.com/BurntSushi/byteorder/issues/65):
91  Add support for `u128`/`i128` types. (Behind the nightly only `i128`
92  feature.)
93* [FEATURE #72](https://github.com/BurntSushi/byteorder/issues/72):
94  Add "panics" and "errors" sections for each relevant public API item.
95* [FEATURE #74](https://github.com/BurntSushi/byteorder/issues/74):
96  Add CI badges to Cargo.toml.
97* [FEATURE #75](https://github.com/BurntSushi/byteorder/issues/75):
98  Add more examples to public API items.
99* Add 24-bit read/write methods.
100* Add `BE` and `LE` type aliases for `BigEndian` and `LittleEndian`,
101  respectively.
102
103Bug fixes:
104
105* [BUG #68](https://github.com/BurntSushi/byteorder/issues/68):
106  Panic in {BigEndian,LittleEndian}::default.
107* [BUG #69](https://github.com/BurntSushi/byteorder/issues/69):
108  Seal the `ByteOrder` trait to prevent out-of-crate implementations.
109* [BUG #71](https://github.com/BurntSushi/byteorder/issues/71):
110  Guarantee that the results of `read_f32`/`read_f64` are always defined.
111* [BUG #73](https://github.com/BurntSushi/byteorder/issues/73):
112  Add crates.io categories.
113* [BUG #77](https://github.com/BurntSushi/byteorder/issues/77):
114  Add `html_root` doc attribute.
115