Re: [Boost-bugs] [Boost C++ Libraries] #2009: suggested resiliency/ease-of-use

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2009: suggested resiliency/ease-of-use
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-06-15 16:33:45

#2009: suggested resiliency/ease-of-use
  Reporter: dave | Owner: nesotto
      Type: Feature Requests | Status: new
 Milestone: Boost 1.36.0 | Component: range
   Version: Boost 1.35.0 | Severity: Problem
Resolution: | Keywords:
Changes (by dave):

 * cc: eric_niebler (added)


 Oh, well, I suppose it's preferable to work with only one of the iterator
 types defined as well. On the other hand, I realize this whole thing is
 really only an issue for a person who is adapting an existing type to the
 Range concept, since the rest of us can use member functions and nested
 typedefs, which is sufficiently economical. You might consider whether it
 is important enough to do anything about.

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:58 UTC