Release 0.1

[pimeys]

This is a ticket for functionality needed before releasing version 0.1 of the crate.

• Support async/await (Async/await #18)
• Have parity in features and usability compared to other AST:s, such as https://pypika.readthedocs.io/en/latest/ (Comparison to PyPika AST #45)
• Make the visitors to allocate less, maybe allocating one slab for the whole query and mutating it while visiting. (Limit allocations when visiting queries #23)
• One interface to all databases. (Better pooling interface #30)
• When converting rows to ResultRow, check if we could copy less and move instead
• Results should be available as a Stream in addition to a fully allocated Vec
• Get needed changes merged to rust-decimal (Support tokio-postgres 0.5.0 and async/await paupino/rust-decimal#203)
• Get needed changes merged to num_cpus (Fix get_physical for AMD ThreadRipper seanmonstar/num_cpus#86)
• Switch to a connection pool that works on stable. (mobc)
• Follow crates.io releases of mysql-async
• Write examples
• Get a fancy and "hip" name for the crate (decided: quaint)
• Replace failure with something implementing std::error::Error

bonus:

• Support async-std!

[tomhoule]

I think we may want both Stream and Vec variants of results. If all APIs return streams, when you want a vec as a consumer of the library, you would collect the stream. Some database drivers will return all the results at once, and we already have a Vec there. In that case you would have a Vec converted to a Stream, and converted back into a Vec, so there's unnecessary copying and allocation.