Hacker News Reader

Right it mentions it when casting to Duck. The post makes it read like casting to `interface { Quack() }` was a problem, when really it was the ignoring of the error return value from that cast.

View on HN

The fact that the error happens _at run time_ is exactly the point. Whether the error is handled or not has nothing to do with the point of the post.

I didn't think anyone was under the impression that Go (or Java, or many other statically-typed languages) have sound type systems. For better/worse there are often intentional and unintentional escape hatches.

Go also has an 'unsafe' package that can mess things up at runtime--don't do that and don't ignore errors.

The language shouldn’t let you silently ignore errors.

It's not silent. It will panic.

but that'll be at runtime

In Go, a runtime panic indicates a programmer error. This means you should not have written that line of code. The solution is to fix the line of code.

Every languages let you ignore errors, Rust included.

Reply on news.ycombinator.com