I remember, a year or three ago, discussing whether or not Encoding
transformers should return an error early, use a substitute character,
or be configurable between the two. I can't remember the details,
though. Marcel, do you?

Maybe we thought that people could write their own ForceDecode
function if they wanted to, although I'd make it a function that
returned a Transformer. Perhaps such a beast should live in

In any case, it seems like a bug that the NewDecoder docs don't match
the implementation. One or the other should change.

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 3 | next ›
Discussion Overview
groupgolang-nuts @
postedDec 2, '15 at 3:21p
activeDec 19, '15 at 2:40p

3 users in discussion

Rin Tohsaka: 1 post Nigel Tao: 1 post Mpvl: 1 post



site design / logo © 2021 Grokbase