On Thu, 13 Oct 2016 05:47:33 -0700 (PDT)
> Thanks, Ian.
> The recover1.go has many great examples to understand the mechanism
> of panic/recover.
> I think I have get it.
> And I still think the spec doc is shallow.
That's because there's the difference between the so-called normative
texts and so-called informative texts. Normative texts intently use dry
language with as minimal wording as possible to not accidently state
more than should have stated. You can found this pattern everywhere --
from civil laws to patents to RFCs and ITU-T recommendations etc.
What's supposedly missing is some piece of documentation accompanying
the spec which would provide informative bits. This could possibly be
a community-provided thing.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.