On Thu, Dec 8, 2011 at 11:44 AM, Olaf van der Spek <ml@vdspek.org> wrote:
On Wed, Dec 7, 2011 at 8:16 PM, Daniel James <dnljms@gmail.com> wrote:
On 6 December 2011 11:25, Olaf van der Spek <ml@vdspek.org> wrote:
On Mon, Dec 5, 2011 at 7:00 PM, Beman Dawes <bdawes@acm.org> wrote:
Also, iterator_traits is viewed as an anachronism by some influential committee members, both because of the lumping of multiple traits into a single class and because of the problems using the current iterator_traits with SFINAE. So you might want to consider a set of replacement traits that follows modern practice. Proposing something like that for Boost would be a good start.
I've never used iterator_traits myself and am not aware of these problems. Got any pointers? :p
These are considered better:
http://www.boost.org/libs/iterator/doc/iterator_traits.html
Separate traits which follow a common convention have proved to be useful in template meta-programming, especially when used with MPL. I'm not sure how C++11 changes things though.
Ticket created: https://svn.boost.org/trac/boost/ticket/6240
Are there any plans to propose Boost Iterator for TR2?
Dave? -- Olaf