Hi, for sure i know final Go proverb -- "Don`t panic". Also Dave.Cheney
"The simple rule of thumb is panic should only be used in truely
exceptional cases, which, as their name suggests are rare."
Also I know there are exist circumstances where explicit panic() call looks
reasonable.
I`d like to know what are the reasons in package reflect to use panic()
instead of return error.
I`m working on not much epic (have about 20000 readers) post about using
panic() in stdlib.
To say
$ grep -r "panic(" $GOROOT/src | wc -l
gave 3218 occurrences of explicit panic() call in stdlib. Really
impressive not panicking)
But design choice in reflect package intriguing me mostly.
Would be much appreciated for hints.
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/a8c61abf-a236-47d9-99a4-ad907412f427n%40googlegroups.com.
