-
Notifications
You must be signed in to change notification settings - Fork 697
What is the reason behind stacktrace being private? #66
Comments
The same question about
|
That example is for documentation only. If I could remove the name of the type and leave the example as clear I would have. If you, the caller, want to assert the type has that behaviour, define an interface or declare one inline and do he type assertion. |
Please send a pr to document causer, this is an oversight. Thanks |
Closed, duplicate of #71 |
But #69 is still open. |
Thanks for bringing that to my attention. On Tue, Jul 19, 2016 at 7:09 PM, Alexey Palazhchenko <
|
According to errors pkg documentation to retrieve the stack trace of an error or wrapper I should try to use interface:
type stackTracer interface { StackTrace() errors.StackTrace }
The stackTracer interface is private. Does it mean, that you don't want it to be an API for errrors library and it can change its behaviour?
The text was updated successfully, but these errors were encountered: