> You'll still get the type errors at runtime because there's no ahead-of-time typechecking happening. That doesn't mean it's just documentation though. It cou

> You'll still get the type errors at runtime because there's no ahead-of-time typechecking happening. That doesn't mean it's just documentation though. It could tell you that something is happening you didn't expect. Like passing a Role where you expected a User. (And if you wanted to operate on both interchangeably you shoulda put an interface on it.) > The main type error you always have to worry about in both languages, though, is accidentally calling functions/methods on nil at runtime. Agreed. Option/Maybe types FTW. The ?-operators sometimes presented as a solution feel very half-baked in comparison (they don't return a new type so just because you remembered to use it on line 10 doesn't mean anything to lines 20, 37 and 82).