Flatten anymap::any out of existence
Namespaces are one honking great idea, but flat is better than nested. anymap::raw still makes sense.
This commit is contained in:
parent
8f041216ba
commit
b07b62fd4d
|
@ -1,5 +1,8 @@
|
|||
# 1.0.0 (unreleased)
|
||||
|
||||
- **Breaking change:** `anymap::any` flattened out of existence:
|
||||
`anymap::any::{Any, CloneAny}` are now found at `anymap::{Any, CloneAny}`.
|
||||
|
||||
- Relicensed from MIT/Apache-2.0 to BlueOak-1.0.0/MIT/Apache-2.0.
|
||||
|
||||
- Increased the minimum supported version of Rust from 1.7.0 to 1.34.0.
|
||||
|
|
|
@ -6,7 +6,8 @@ use std::any::TypeId;
|
|||
use std::marker::PhantomData;
|
||||
|
||||
use raw::RawMap;
|
||||
use any::{UncheckedAnyExt, IntoBox, Any};
|
||||
use any::{UncheckedAnyExt, IntoBox};
|
||||
pub use any::{Any, CloneAny};
|
||||
|
||||
macro_rules! impl_common_methods {
|
||||
(
|
||||
|
@ -85,7 +86,7 @@ macro_rules! impl_common_methods {
|
|||
}
|
||||
}
|
||||
|
||||
pub mod any;
|
||||
mod any;
|
||||
pub mod raw;
|
||||
|
||||
/// A collection containing zero or one values for any given type and allowing convenient,
|
||||
|
|
Loading…
Reference in a new issue