Releases: bitflags/bitflags
Releases · bitflags/bitflags
1.2.1
- Remove extraneous
#[inline]
attributes (#194)
1.2.0
-
Fix typo: {Lower, Upper}Exp - {Lower, Upper}Hex (#183)
-
Add support for "unknown" bits (#188)
1.1.0
This is a re-release of 1.0.5
, which was yanked due to a bug in the RLS.
1.0.5
-
Use compiletest_rs flags supported by stable toolchain (#171)
-
Put the user provided attributes first (#173)
-
Make bitflags methods const
on newer compilers (#175)
1.0.3
- Improve zero value flag handling and documentation (#157, thanks @Alex-Addy)
1.0.2
- 30% improvement in compile time of bitflags crate (#156)
- Documentation improvements (#153)
- Implementation cleanup (#149)
1.0.1
- Add support for
pub(restricted)
specifier on the bitflags struct (#135)
- Optimize performance of
all()
when called from a separate crate (#136)
1.0.0
-
[breaking change] Macro now generates associated constants (#24)
-
[breaking change] Minimum supported version is Rust 1.20, due to usage of associated constants
-
After being broken in 0.9, the #[deprecated]
attribute is now supported again (#112)
-
Other improvements to unit tests and documentation (#106 and #115)
How to update your code to use associated constants
Assuming the following structure definition:
bitflags! {
struct Something: u8 {
const FOO = 0b01,
const BAR = 0b10
}
}
In 0.9 and older you could do:
let x = FOO.bits | BAR.bits;
Now you must use:
let x = Something::FOO.bits | Something::BAR.bits;
0.9.1
- Fix the implementation of Formatting traits when other formatting traits were present in scope (#105)