update metadata

Author: NyxCode

Cargo.toml

@@ -1,10 +1,13 @@
 [package]
 name = "proxy-enum"
-version = "0.1.1"
+version = "0.1.2"
 authors = ["Moritz Bischof <[email protected]>"]
 edition = "2018"
 description = "Emulate dynamic dispatch and sealed classes using a proxy enum, which defers all method calls to its variants."
 license = "MIT"
+readme = "README.md"
+repository = "https://github.com/NyxCode/proxy-enum"
+keywords = ["proxy", "enum", "sealed", "variant"]
 
 [lib]
 proc-macro = true

README.md

@@ -1,4 +1,6 @@
 # proxy-enum
+![Crates.io](https://img.shields.io/crates/d/proxy-enum?style=flat-square)
+![](https://docs.rs/mio/badge.svg)  
 
 Emulate dynamic dispatch and ["sealed classes"](https://kotlinlang.org/docs/reference/sealed-classes.html) using a proxy enum, which defers all method calls to its variants.
 
@@ -7,7 +9,7 @@ In rust, dynamic dispatch is done using trait objects (`dyn Trait`).
 They enable us to have runtime polymorphism, a way of expressing that a type implements a
 certain trait while ignoring its concrete implementation.
 
-```
+```rust
 let animal: &dyn Animal = random_animal();
 animal.feed(); // may print "mew", "growl" or "squeak"
 ```
@@ -18,7 +20,7 @@ getting a concrete implementation back from a trait object (downcasting) is pain
 
 If you know there are only a finite number of implentations to work with, an `enum` might be
 better at expressing such a relationship:
-```
+```rust
 enum Animal {
     Cat(Cat),
     Lion(Lion),
@@ -38,7 +40,7 @@ Rust, however, does *not*.
 `proxy-enum` simplifies working with such types using procedural macros.
 
 ## Usage
-```
+```rust
 #[proxy_enum::proxy(Animal)]
 mod proxy {
     enum Animal {
@@ -54,7 +56,7 @@ mod proxy {
 }
 ```
 This will expand to:
-```
+```rust
 mod proxy {
     enum Animal {
         Cat(Cat),
@@ -75,7 +77,7 @@ mod proxy {
 ```
 This, however, will only compile if `Cat`, `Lion` and `Mouse` all have a method called `feed`.
 Since rust has traits to express common functionality, trait implentations can be generated too:
-```
+```rust
 #[proxy_enum::proxy(Animal)]
 mod proxy {
     enum Animal {
@@ -95,7 +97,7 @@ mod proxy {
 Since the macro has to know which methods the trait contains, it has to be defined within the
 module. However, implementations for external traits can be generated too:
 
-```
+```rust
 #[proxy_enum::proxy(Animal)]
 mod proxy {
     enum Animal {