For example, if you do a runtime type assertion to see if a variable satisfies an interface:
v, ok := x.(T)
http://golang.org/ref/spec#Type_assertionsIf you "monkey-patch" x to satisfy T in another package, the value of ok may change.
Hmm I can kind of see what you mean, but I don't see it as a big of a problem.
If you make package A depend on package B, package B monkey-patches x with method Foo so now x is a Fooer
x now satisfies the Fooer interface in package A, well that seems ok. You imported B after all. In things that don't import B, x doesn't satisfy Fooer. Is this unexpected behavior? If B depends on C, C's x won't satisfy Fooer right?
I'm reading through the embedded types now. I am new to golang so this one is lost on me. I thought if you wanted your own methods on a type from another package, you just aliased it with your own type def.
though it looks like there's some kinda prototyping behavior being described here?