John-John Tedro

I don't know if this falls under here (or if there's a duplicate issue or any prior discussion), but due to the way that the cargo resolver currently works removing...

Related: #191

Note I believe OP is referencing the use of spawn and timer, which currently are hard dependencies on a tokio runtime. Use of `tokio::spawn`: https://github.com/blackbeam/mysql_async/blob/master/src/conn/pool/mod.rs#L203 Use of `tokio::timer`: https://github.com/blackbeam/mysql_async/blob/master/src/conn/pool/mod.rs#L641 Unfortunately...

Yeah. My goal is to author a set of traits and data structures that can be used across audio libraries in the ecosystem. I'm currently [holding off on GATs landing](https://github.com/udoprog/audio/tree/gat),...

I am definitely looking forward to it!

Yeah. This is just for experimentation. I don't intend to submit anything upstream until this crate is done. I elaborated more in #3. But, we can certainly make it easier...

Good to know about the workaround, but I don't know how useful it is since the cost is getting rid of useful documentation :(.

Works fine with the following environment. ``` Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T13:57:37+02:00) Maven home: /home/udoprog/usr/apache-maven-3.3.3 Java version: 1.8.0_60, vendor: Oracle Corporation Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre Default locale: en_US, platform encoding: UTF-8...

My bad, missed to remove `useIncrementalCompilation`. I can indeed produce this.

Another interesting issue is that we seem to be getting an UTF-16 BOM:  This is from a `README.md` generated using `cargo-readme` on Windows.