The concurrent map access checks in Go1.6rc1 have already uncovered one such bug in my code. Love it!

Oh, and I've already made use of the whitespace-stripping in text templates, too! :)

One thing I was worried about from the focus on reducing maximum GC pause times (i.e. latency) was that this might negatively affect GC throughput. For example, maybe the pauses are shorter but there are many more of them. The project I'm working on at the moment exercises the GC heavily but is not concerned with latency (it's bulk data-processing), and I didn't see any significant regression in performance/throughput from 1.5 to 1.6rc1. So, yay.