undefined | Better HN

0 pointscodeflo12y ago0 comments

That introduces a new named type though, i.e., the "any" in your package is different from the "any" in mine, which is not what I want.

(Unless I'm mistaken here, which might very well be the case.)

0 comments

Anyway, that's the point of go's type inference- if the object implements the necessary parts of the interface, it counts as that kind of object.

j / k navigate · click thread line to collapse

0 pointscodeflo12y ago0 comments

That introduces a new named type though, i.e., the "any" in your package is different from the "any" in mine, which is not what I want.

(Unless I'm mistaken here, which might very well be the case.)

Anyway, that's the point of go's type inference- if the object implements the necessary parts of the interface, it counts as that kind of object.

j / k navigate · click thread line to collapse