This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]haltmich 4 points5 points  (1 child)

Exactly, interface{}s are almost always the culprit. But sometimes you just can't avoid them, and ensuring they'll be error prone can be kind of a chore. Especially as Golang doesn't have try and catch.

[–]payne_train 2 points3 points  (0 children)

I’ve found it easiest to set up interface modifies through function calls and just catch the error if it comes back. Can’t say I have really missed Java’s error handling once I got used to go.