Discussion on: The Problem with Interfaces, and how Go Fixed it

Replies for: If I understand correctly Go isn't even strictly duck typed. The type inference doesn't happen at runtime but at compile time, giving very clear c...

The only time it would result in a runtime error is when casting, as per every staticly typed language.

That's what I thought! So I really don't get all this duck typing trash talk some people are throwing around in regards to Go