FAQ
I think this is too broad a fix. Let's fix the (apparently few) panics
taking strings instead of panicking for everything.

Note that the 'case error' in your switches covers case runtime.Error
too, so this is squelching runtime.Errors that used to be panics.

I only see one panic(" in the tree that isn't unreachable:
scanner.go:610: panic("json: invalid use of scanner")

The test cases in issues 4474 and 4222 are real bugs in the way json
uses reflect: it shouldn't be asking reflect to do those things. We
should fix those calls, not turn reflect's panics into returned errors.

https://codereview.appspot.com/6938045/

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 2 | next ›
Discussion Overview
groupgolang-dev @
categoriesgo
postedDec 17, '12 at 12:51a
activeDec 17, '12 at 9:37a
posts2
users2
websitegolang.org

2 users in discussion

Dave: 1 post Rsc: 1 post

People

Translate

site design / logo © 2022 Grokbase