Re:Error stack traces in Go with x/xerror
by anonymoushn on Tuesday August 24, 2021 @03:51AM
(#28286096)
The above code is probably caused by checked exceptions. In particular, the user wants to implement some interface or override some method, but that method wasn't declared to throw a particular type of exception because the people who wrote it hate extensibility and never want their software to be used in a way they didn't anticipate, so the new implementation can't throw it either.
[ Parent
| on HN ]
There are no comments on this comment yet.