mirror of
https://github.com/openharmony/third_party_rust_bitflags.git
synced 2026-07-20 23:46:15 -04:00
Bump to 0.9.0
This commit is contained in:
+1
-1
@@ -4,7 +4,7 @@ name = "bitflags"
|
||||
# NB: When modifying, also modify:
|
||||
# 1. html_root_url in lib.rs
|
||||
# 2. number in readme (for breaking changes)
|
||||
version = "0.8.0"
|
||||
version = "0.9.0"
|
||||
authors = ["The Rust Project Developers"]
|
||||
license = "MIT/Apache-2.0"
|
||||
keywords = ["bit", "bitmask", "bitflags"]
|
||||
|
||||
@@ -13,7 +13,7 @@ Add this to your `Cargo.toml`:
|
||||
|
||||
```toml
|
||||
[dependencies]
|
||||
bitflags = "0.8"
|
||||
bitflags = "0.9"
|
||||
```
|
||||
|
||||
and this to your crate root:
|
||||
|
||||
+3
-3
@@ -11,8 +11,8 @@
|
||||
//! A typesafe bitmask flag generator useful for sets of C-style bitmask flags.
|
||||
//! It can be used for creating typesafe wrappers around C APIs.
|
||||
//!
|
||||
//! The `bitflags!` macro generates a `struct` that manages a set of flags. The
|
||||
//! flags should only be defined for integer types, otherwise unexpected type
|
||||
//! The `bitflags!` macro generates a `struct` that manages a set of flags. The
|
||||
//! flags should only be defined for integer types, otherwise unexpected type
|
||||
//! errors may occur at compile time.
|
||||
//!
|
||||
//! # Example
|
||||
@@ -218,7 +218,7 @@
|
||||
|
||||
#![no_std]
|
||||
|
||||
#![doc(html_root_url = "https://docs.rs/bitflags/0.8.2")]
|
||||
#![doc(html_root_url = "https://docs.rs/bitflags/0.9.0")]
|
||||
// When compiled for the rustc compiler itself we want to make sure that this is
|
||||
// an unstable crate.
|
||||
#![cfg_attr(rustbuild, feature(staged_api))]
|
||||
|
||||
Reference in New Issue
Block a user