Hi, Just a quick question. I know it's well accepted that panics leaking to the public API of a library is generally a no-go.
Yet, are there any exception to the rule? For instance, I have a library that instantiates some database prepared statements (so, the majority of the elements are instantiated and used in the main function). I would like to panic instead of returning an error because, if db.Prepare(q) returns an error, there is no point in continuing, the error is barely recoverable. Besides, it will allow for a better looking API so to speak. Any comments? -- 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/25204eae-8550-4a78-94a3-6a63e9906f20%40googlegroups.com.
