go – s/o golang example with infinite for / channel workers

I whipped this up as an example of how infinite loops can often be used to great effect in golang, and also to discuss closing channels and worker communications. It was strictly off the cuff, but I was curious if anybody would like to offer a critique. In particular, I feel as though inflight is a crude implementation detail. I’ve done it many times, and looking at wait group implementation, seems like it is a synchronized version of the same thing.

package main

import (

func doStuff(datachan <-chan map(string)string, reschan chan<- int) {
  for {
    data, ok := <-datachan
    if !ok {
      log.Print("Channel closed.")
    log.Printf("Data had %d length: %+v", len(data), data)

const workers = 3

func main() {
  var datachan = make(chan map(string)string)
  var reschan = make(chan int)
  var inflight = 0
  var inputs = ()map(string)string {
    map(string)string{ "hi": "world" },
    map(string)string{ "bye": "space", "including": "moon" },
    map(string)string{ "bye": "space", "including": "moon" },
    map(string)string{ },
    map(string)string{ },
  // an inline funciton definition can change inflight within main()'s scope
  processResults := func (res int) {
    log.Printf("Main function got result %d", res)
  // start some workers
  for i := 0; i < workers; i++{
    go doStuff(datachan, reschan)
  for _, data := range inputs {
      //Select allows reading from reschan if datachan is not available for
      // writing, thus freeing up a worker to read from datachan next loop
      written := false
      for written  != true {
        select {
          case res := <-reschan:
          case datachan <- data:
            written = true
  for inflight > 0 {