Improved the information about the crate in Cargo.toml

Author: frol

Cargo.toml

@@ -1,14 +1,20 @@
 [package]
 name = "flatc-rust"
-version = "0.1.1-alpha.0"
+version = "0.1.1"
 authors = ["Vlad Frolov <frolvlad@gmail.com>"]
+edition = "2018"
 license = "MIT/Apache-2.0"
 homepage = "https://github.com/frol/flatc-rust"
 repository = "https://github.com/frol/flatc-rust"
-description = """
-FlatBuffers flatc command as API
-"""
-edition = "2018"
+description = "FlatBuffers flatc command as API"
+documentation = "https://docs.rs/flatc-rust/*/flatc-rust"
+readme = "README.md"
+keywords = ["flatbuffers", "flatc", "compiler", "code-generation"]
+categories = ["development-tools::build-utils", "development-tools", "api-bindings", "parser-implementations"]
+include = ["/src/**/*", "/Cargo.toml", "/LICENSE-MIT", "/LICENSE-APACHE", "/README.md"]
+
+[badges]
+travis-ci = { repository = "frol/flatc-rust" }
 
 [dependencies]
 log = "0.*"

src/lib.rs

@@ -34,7 +34,7 @@
 //! # try_main().ok();
 //! ```
 //!
-//! ## Build scripts (`build.rs`) integration example
+//! ## Build scripts (`build.rs`) integration
 //!
 //! It is common to have FlatBuffers specifications as a single source of truth, and thus, it is
 //! wise to build up-to-date helpers when you build your project. There is a built-in support for
@@ -82,6 +82,12 @@
 //!
 //! [build scripts in Cargo]: https://doc.rust-lang.org/cargo/reference/build-scripts.html
 //! [example projects]: https://github.com/frol/flatc-rust/tree/master/examples
+//!
+//! ## Usage in external projects
+//!
+//! There is [a benchmark of FlatBuffers vs other serialization
+//! frameworks](https://github.com/erickt/rust-serialization-benchmarks/pull/7), which is based on
+//! `flatc-rust` integration.
 
 #![deny(missing_docs)]
 #![deny(unsafe_code)]