golang-structs-interfaces

When designing Go types, choose struct embedding to promote methods and satisfy interfaces implicitly, but use named fields when you need to prevent external callers from overriding embedded state or invoking embedded methods directly.

Use pointer receivers when struct methods need to mutate state or handle large structs efficiently, and use value receivers to protect struct immutability or when working with small, copy-safe types.

Use type assertions and type switches to extract dynamic behavior from interfaces when needed, ensuring safe execution by checking the `ok` return value or using the comma-ok pattern to prevent runtime panics during type conversion.

You need interface segregation in Golang when consumers are forced to depend on methods they do not use; splitting large interfaces into smaller, consumer-specific contracts prevents unused method dependencies and simplifies mocking.