These issues were intended for 0.2.16 but didn't get resolved in time.
We should consider targeting these for inclusion in 1.0