Versioning issue with Rust 2018 changes

[SilentByte]

The release should have been a feature release, because a crate might depend on the new functionality introduced with 1.0.2 (being able to use name_of!(type ...) without importing name_of_type!).

This might be an issue in the following situation:

Given that crate A depends on crate B and the following versions:

crate	Cargo.toml	Cargo.lock
crate A	-	1.0.1
crate B	1.0	-

When crate B uses the new feature from 1.0.2, crate A fails to build.

I recommend releasing two new versions:

• 1.0.3 (Identical to 1.0.1)
• 1.1.0 (Identical to 1.0.2)

Also 1.0.2 should be yanked from crates.io.

---

Co-written-by: @bash

Originally posted by @jeremystucki in #1 (comment)

[SilentByte]

Should be fixed now, thanks again for the advice!