Consider adding a separate algorithm for saturating_increment

[chriskohlhoff]

[chriskohlhoff]

I.e. the increment used in places like this:

size_t n = 0;
while (run_one())
  if (n != numeric_limits<size_t>::max())
    ++n;

[chriskohlhoff]

Pre-Lenexa Summary

[io_service.io_service]

Several effects clauses contain code like this:

if (n != numeric_limits<size_t>::max())
  ++n;

The suggestion was that we include an algorithm for this as part of the proposal.

Alternatively, we could simplify the specification by specifying SATURATING_INCREMENT (i.e. something like DECAY_COPY). Or we could just leave it as-is.