3 ms·
> It's often not clear which exceptions can be thrown from a function Go 1 failed to solve that as well. "error" as an interface tells me nothing about what co
by kemitche 8y ago
> It's often not clear which exceptions can be thrown from a function
Go 1 failed to solve that as well. "error" as an interface tells me nothing about what could go wrong with a function call. Go 2 is not looking like it will solve it either. I am happy with the proposals, but I know I'm still going to be looking at godocs and be forced to dig into source code to find out what error types actually come back, and hope they don't change from version to version.
- weberc2 8y agoI agree with this. It would be great if we didn't have to give up any type safety with error returns. Even still, this is relatively minor when you remember that people write code in JS, Python, Ruby, etc with zero type safety.
- IshKebab 8y agoThis is true. However it is better in one big way - you at least know whether or not it will return an error at all.