Anonymous interfaces

April 13, 2023

Today we pick up the second half of an example we started with yesterday:

Similarly, consider this interface specification, which appears within a type declaration to define an interface called Locker:

type Locker interface {

If S1 and S2 also implement

func (p T) Lock() { … }
func (p T) Unlock() { … }

they implement the Locker interface as well as the File interface.

We’ve already discussed that a single type may automatically satisfy multiple interfaces, so there’s not much to add here.

What I would like to elaborate on, though, is that an interface type doesn’t necissarily have to be named, as it is in this example. Anonymous interfaces are entirely usable as well. Let’s look at an example, building on the above code.

This code references the above Locker type in a type assertion, to see whether variable x implements the Locker interface, and if so, calls Lock() on the variable.

if locker, ok := x.(Locker); ok {

We can do the same without explicitly declaring that Locker type, though:

if locker, ok := x.(interface{ Lock() }); ok {

Here we inline the interface declaration anonymously (I’ve also omitted the Unlock() method, since I’m not calling it in the example.)

Quotes from The Go Programming Language Specification Version of December 15, 2022

Share this

Related Content

Implementing an interface

It feels like it’s been a month since we started on interfaces. Today we’re covering the final section on this topic! Implementing an interface A type T implements an interface I if T is not an interface and is an element of the type set of I; or T is an interface and the type set of T is a subset of the type set of I. A value of type T implements an interface if T implements the interface.

Recursive interfaces

Check out this week’s episode of the Cup o’ Go podcast: What the ʕ◔ϖ◔ʔ? New merch, TDD book interview with Adelina Simion, and more You can probably guess Go’s rules about recursively embedding interfaces. In short: It’s not allowed. General interfaces … An interface type T may not embed a type element that is, contains, or embeds T, directly or indirectly. // illegal: Bad may not embed itself type Bad interface { Bad } // illegal: Bad1 may not embed itself using Bad2 type Bad1 interface { Bad2 } type Bad2 interface { Bad1 } // illegal: Bad3 may not embed a union containing Bad3 type Bad3 interface { ~int | ~string | Bad3 } // illegal: Bad4 may not embed an array containing Bad4 as element type type Bad4 interface { [10]Bad4 } Note however, that, an interface method may refer to the interface itself.

Interfaces as type constraints

If you’ve been playing around with interface types while reading about them for the last couple of weeks, you have probably noticed something: Many of the interface types described don’t work as variables. Here we see why: General interfaces … Interfaces that are not basic may only be used as type constraints, or as elements of other interfaces used as constraints. They cannot be the types of values or variables, or components of other, non-interface types.