Making peek entirely dependent on metadata access doesn't feel right.

Maybe peek could take an optional closure parameter? And only populate metadata if the closure is not provided? Or it could populate metadata regardless.

If peek can only be used with metadata access, is there any advantage over having it as a separate command rather than metadata access --peek?

Alternatively, can we envision a use-case (I can't at the moment) where it would be useful to have:

peek 2 {|p|
  some conditional based on peeked value {
    metadata access {
      ..
    }
  }
}

Granted, that adds two levels of nesting, and again, I'm not even sure there's a use-case.

@NotTheDr01ds I think having a separate command is better because:

• it avoids adding flags in favor of composing commands
• peek as a standalone command has much better discoverability. I don't think anyone would go straight for metadata access when they want to peek stream items without collecting.

peek as a standalone command is fine. Just make it not entirely dependent on metadata access. An optional closure argument would resolve that