CC @jba @neild

We originally had an errors.Wrapper interface definition:

type Wrapper interface {
  Unwrap() error
}

There was substantial debate over whether this type should be called Wrapper (since a Wrapper wraps another error) or Unwrapper (since an Unwrapper has an Unwrap method). In the end, we removed the Unwrapper type on the grounds that we could add it later when we had more clarity on the best name for it.

We considered errors.Iser and errors.Aser types:

type Iser interface {
  Is(error) bool
}

type Aser interface {
  As(interface{}) bool
}

My recollection is that we didn't like the names and couldn't think of many, if any, cases when you would use the Iser and Aser types directly.

@neild Thanks! Good to know it was on the grounds of not having a good name instead of wanting to not expose these.

Hopefully this issue serves as some docs until something is eventually picked.

A named interface is more-constrained than an anonymous interface, as comparisons are currently taking the name of the type into account with a named interface.

How will this impact the proposal?

declined in #39539