Release 0.2

README.md

@@ -13,21 +13,24 @@ A radioactive stabilization of the [`ptr_meta` RFC][rfc].
 
 [rfc]: https://rust-lang.github.io/rfcs/2580-ptr-meta.html
 
-## Usage
+# Usage
 
-### Sized types
+## Sized types
 
-Sized types already have `Pointee` implemented for them, so most of the time you won't have to worry
-about them. However, trying to derive `Pointee` for a struct that may or may not have a DST as its
-last field will cause an implementation conflict with the automatic sized implementation.
+All `Sized` types have `Pointee` implemented for them with a blanket implementation. You do not
+need to derive `Pointee` for these types.
 
-### `slice`s and `str`s
+## `slice`s and `str`s
 
 These core types have implementations built in.
 
-### Structs with a DST as its last field
+# `dyn Any`
 
-You can derive `Pointee` for last-field DSTs:
+The trait object for this standard library type comes with an implementation built in.
+
+## Structs with a DST as its last field
+
+You can derive `Pointee` for structs with a trailing DST:
 
 ```rust
 use ptr_meta::Pointee;
@@ -39,9 +42,14 @@ struct Block<H, T> {
 }
 ```
 
-### Trait objects
+Note that this will only work when the last field is guaranteed to be a DST. Structs with a
+generic last field may have a conflicting blanket impl since the generic type may be `Sized`. In
+these cases, a collection of specific implementations may be required with the generic parameter
+set to a slice, `str`, or specific trait object.
+
+## Trait objects
 
-You can generate a `Pointee` for trait objects:
+You can generate a `Pointee` implementation for trait objects:
 
 ```rust
 use ptr_meta::pointee;

ptr_meta/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ptr_meta"
-version = "0.1.4"
+version = "0.2.0"
 authors = ["David Koloski <[email protected]>"]
 edition = "2018"
 description = "A radioactive stabilization of the ptr_meta rfc"
@@ -14,7 +14,7 @@ readme = "crates-io.md"
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
 
 [dependencies]
-ptr_meta_derive = { version = "=0.1.4", path = "../ptr_meta_derive" }
+ptr_meta_derive = { version = "=0.2.0", path = "../ptr_meta_derive" }
 
 [features]
 default = ["std"]

ptr_meta/crates-io.md

@@ -1,24 +1,25 @@
-# ptr_meta
-
 A radioactive stabilization of the [`ptr_meta` RFC][rfc].
 
 [rfc]: https://rust-lang.github.io/rfcs/2580-ptr-meta.html
 
-## Usage
+# Usage
 
-### Sized types
+## Sized types
 
-Sized types already have `Pointee` implemented for them, so most of the time you won't have to worry
-about them. However, trying to derive `Pointee` for a struct that may or may not have a DST as its
-last field will cause an implementation conflict with the automatic sized implementation.
+All `Sized` types have `Pointee` implemented for them with a blanket implementation. You do not
+need to derive `Pointee` for these types.
 
-### `slice`s and `str`s
+## `slice`s and `str`s
 
 These core types have implementations built in.
 
-### Structs with a DST as its last field
+# `dyn Any`
+
+The trait object for this standard library type comes with an implementation built in.
 
-You can derive `Pointee` for last-field DSTs:
+## Structs with a DST as its last field
+
+You can derive `Pointee` for structs with a trailing DST:
 
 ```rust
 use ptr_meta::Pointee;
@@ -30,9 +31,14 @@ struct Block<H, T> {
 }
 ```
 
-### Trait objects
+Note that this will only work when the last field is guaranteed to be a DST. Structs with a
+generic last field may have a conflicting blanket impl since the generic type may be `Sized`. In
+these cases, a collection of specific implementations may be required with the generic parameter
+set to a slice, `str`, or specific trait object.
+
+## Trait objects
 
-You can generate a `Pointee` for trait objects:
+You can generate a `Pointee` implementation for trait objects:
 
 ```rust
 use ptr_meta::pointee;

ptr_meta/src/impls.rs

@@ -1,5 +1,5 @@
-use core::any::Any;
 use crate::{DynMetadata, Pointee};
+use core::any::Any;
 
 impl Pointee for dyn Any {
     type Metadata = DynMetadata<dyn Any>;