RELEASE: v0.1.0 release prep

- Documentation fixes for operator precendence changes.
- Mark this as a v0.1.0 change for with potential breaking api changes.
- Cleanup TODO documentation.

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name        = "ucg"
-version     = "0.0.4"
+version     = "0.1.0"
 authors     = ["Jeremy Wall <jeremy@marzhillstudios.com>"]
 description = "A configuration generation grammar."
 repository  = "https://github.com/zaphar/ucg"

TODO.md

@@ -29,4 +29,5 @@ Some options here could be:
 * Allow trailing commas.
 * Flags should allow different seperators for prefixed flags.
 * YAML export
+* HCL export
 * Integration Testing framework

src/lib.rs

@@ -270,9 +270,8 @@
 //!
 //! ##### Operator Precedence
 //!
-//! ucg operators evaluate the right side first. If you want to enforce a different
-//! order of operations you will need to use parentheses to group them. This is
-//! most evident when mixing numeric and comparison operators.
+//! UCG binary operators follow the typical operator precedence for math. `*` and `/` are higher precendence than
+//! `+` and `-` which are higher precedence than any of the comparison operators. 
 //!
 //! ```ucg
 //! 1+1 == 2; // this will be a type error. The + expects an integer but it has a boolean expression