Yeah, writev seems different enough from write to merit a different Go interface. Hence the hypothetical WriteStrings method, for example, instead of building a

Yeah, writev seems different enough from write to merit a different Go interface. Hence the hypothetical WriteStrings method, for example, instead of building around Writer. Whether it'd be worth futzing to get templating with less copying depends on whether you can measure much practical benefit over bytes.Buffer, I guess. Takes round tuits to see. Mostly just thought writev was neat; it seems cool that it's theoretically possible to write Go code using it too.