有没有在Go中设计信号或事件API的首选方法？

Question

I am designing a package where I want to provide an API based on the observer pattern: that is, there are points where I'd like to emit a signal that will trigger zero or more interested parties. Those interested parties shouldn't necessarily need to know about each other.

I know I can implement an API like this from scratch (e.g. using a collection of channels or callback functions), but was wondering if there was a preferred way of structuring such APIs.

In many of the languages or frameworks I've played with, there has been standard ways to build these APIs so that they behave the way users expect: e.g. the g_signal_* functions for glib based applications, events and addEventListener() for JavaScript DOM apps, or multicast delegates for .NET.

Is there anything similar for Go? If not, is there some other way of structuring this type of API that is more idiomatic in Go?

Answer 1

I would say that a goroutine receiving from a channel is an analogue of an observer to certain extent. An idiomatic way to expose events in Go would be thus IMHO to return channels from a package (function). Another observation is that callbacks are not used too often in Go programs. One of the reasons is the also the existence of the powerful select statement.

As i final note: some people (me too) consider GoF patterns as Go antipatterns.