Subscriber

Publishers publish, and subscribers subscribe. You might also hear a few alternative terms:

Publisher = Producer = Sender
Subscriber = Consumer = Receiver

Assignment

Let's further separate the "subscribing" logic from the "distribution" logic.

Complete the doBattles method on the user type. It takes a channel that receives move structs. It should return a slice of pieces, []piece, that represents pieces in battle.

For each message in the subCh channel, compare the moving piece's location to the location of all pieces the user controls
Find and list battles. If any two pieces are in the same location, a battle occurs:
- List pieces in battle in the order of the messages received
- List the user's pieces in battle from index 0->end
- Don't worry about deduplication

package main

func (u user) doBattles(subCh <-chan move) []piece {

// ?

}

// don't touch below this line

type user struct {

name string

pieces []piece

}

type move struct {

userName string

piece piece

}

type piece struct {

location string

name string

}

func (u user) march(p piece, publishCh chan<- move) {

publishCh <- move{

userName: u.name,

piece: p,

}

func distributeBattles(publishCh <-chan move, subChans []chan move) {

for mv := range publishCh {

for _, subCh := range subChans {

subCh <- mv

}