KITFORMA · EDITORIAL ANSWER
Why does *T implement my Go interface while T does not?
KitForma editorial guide. Interface satisfaction depends on method sets. Pointer-receiver methods can make the pointer type satisfy an interface without giving the value type the same set.
Step-by-step answer
Interface satisfaction depends on method sets. Pointer-receiver methods can make the pointer type satisfy an interface without giving the value type the same set.
Pass a pointer when shared identity or mutation is intended. Use value receivers only when copying fits the type, especially if it contains synchronization state. Do not alter receiver types merely to silence an interface assignment.
Add a compile-time assertion for the intended implementation, such as
var _ io.Reader = (*MyReader)(nil) with the real type and imports. Test through the interface. Automatic address-taking in certain direct method calls does not make every value assignment to an interface equivalent to assigning its pointer.Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.