code review 5694098: encoding/json: drop MarshalForHTML; gofix calls to Marshal.

encoding/json: drop MarshalForHTML; gofix calls to Marshal.

I've elected to omit escaping the output of Marshalers for now.
I haven't thought through the implications of that;
I suspect that double escaping might be the undoing of that idea.

Fixes issue 3127.

[dsymonds, 2012-02-28 00:02:38]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://go.googlecode.com/hg/

[r, 2012-02-28 00:06:54]

LGTM

[dsymonds, 2012-02-28 00:41:22]

*** Submitted as http://code.google.com/p/go/source/detail?r=0e8f0096e631 ***

encoding/json: drop MarshalForHTML; gofix calls to Marshal.

I've elected to omit escaping the output of Marshalers for now.
I haven't thought through the implications of that;
I suspect that double escaping might be the undoing of that idea.

Fixes issue 3127.

R=golang-dev, r
CC=golang-dev
http://codereview.appspot.com/5694098

[rsc, 2012-02-28 16:55:35]

Please send a follow-up CL doing the escaping.
There is no concern about double-escaping, because
the escaping rewrites < > & into sequences that do
not mention those (\u00xx), so escaping twice is
no different than escaping once.

Now that we've removed MarshalForHTML it is
especially important that the escaping be done always.

It would be good to get this in before the weekly is tagged.