It's similar, but not quite! Usually when people refer to duck typing, it's runtime (ie checking if something is a type by checking if it has a certain method at runtime). Go's interfaces are determined at compile-time rather than runtime.
True but the problem is the implicit part. Implicit is bad because.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's similar, but not quite! Usually when people refer to duck typing, it's runtime (ie checking if something is a type by checking if it has a certain method at runtime). Go's interfaces are determined at compile-time rather than runtime.
True but the problem is the implicit part. Implicit is bad because.