反映。选择功能需要为什么？ 我认为是因为通道必须是反射值？

Question

Under what cases would reflect.Select be needed?

I have found examples, but the use of Select seems contrived.

Any example where reflect.Select is necessary over normal Select?

Answer 1

There was a write-up recently from the guys at MongoDB. Apparently this code is in production use in their mongodump utility.

The specific code that uses reflect.Select looks like this (from the article):

// Run multiplexer until it receives an EOF on the control channel.
func (mux *Multiplexer) Run() {
    for {
        index, value, recv := reflect.Select(mux.selectCases)
        EOF := !recv
        // note that the control channel is always at index 0
        if index == 0 {
            if EOF {
                return
            }
            muxInput, _ := value.Interface().(*muxInputSource)
            mux.selectCases = append(mux.selectCases, reflect.SelectCase{
                Dir:  reflect.SelectRecv,
                Chan: reflect.ValueOf(muxInput.collection),
                Send: reflect.Value{},
            })
        } else {
            if EOF {
                mux.writeEOF()
                mux.selectCases = append(mux.selectCases[:index], mux.selectCases[index+1:]...)
            } else {
                document, _ := value.Interface().([]byte)
                mux.writeDocument(document)[]
            }
        }
    }
}

The reasons I can think that they use reflect.Select instead of a straight select:

• The number of goroutines (and therefore the number of channels) is determined at runtime (using the -j flag). In fact, it seems to change dynamically with append. (credit to @cnicutar's comment)
• The type of the channel is determined at runtime. This allows their muxInput.collection type to be anything it wants. (credit to @JimB's comment)