Sometimes I want to use comments because I'm doing something vaguely algorithmic, and I know some readers won't follow the code.

I'm trying to think of a good example, maybe something like a pointer window based function (off the top of my head)

(This isn't real code. Don't get hung up on it)

    func DedupeStrings(ss []string) []string {
      if len(ss) < 2 {
        return ss
      }
      ss = strings.Sort(ss)

      u := 1 // index of end of "uniques" set
      for i := 1; i < len(ss); i++ {
        // Consume until new value
        if ss[i] == ss[i-1] {
          continue
        }
        // Put new value in 'uniques' set
        ss[u] = sorted[i]
        u++
      }
      // Final state: all unique items are positioned 
      // left of 'u' index
      return ss[:u]
    }

People will quibble, but

- I'm not convinced you could change the variable names without harming clarity. Would a name like uniquesEndIndex really be any clearer? It adds noise to the code and still doesn't satisfy a confused reader

- I don't want to use function calls for documentation, eg putInUniques(). I'm doing it this way because I want it to run really quick.