Check whether write!() error propagation is optimized away

[mstange]

We're write!ing into a Vec, and allocation is infallible, so this should never return an error. We should find out if the compiler optimizes away the error handling here, or if not, find out whether it's a performance problem and maybe do something different.

[encounter]

Looks like this was resolved by #78.