Naming Parameters

While it’s not strictly required for the compiler, you should name the parameters in your interface method signatures to improve readability and documentation.

Why name them?

Consider these two versions of the same interface:

// Vague: What are these strings?
type Copier interface {
    Copy(string, string) int
}

// Clear: We know what to pass where
type Copier interface {
    Copy(sourceFile string, destinationFile string) (bytesCopied int)
}

Self-Documenting Code

Naming the parameters makes it clear to other developers (and your future self) what the interface expects without needing to look at external documentation or implementation details.