Subject: [boost] [detail] Bug in is_postfix_incrementable
From: Edward Diener (eldiener_at_[hidden])
Date: 2015-03-31 19:22:16
There is a rather bad bug in is_postfix_incrementable in the
detail/is_incrementable.hpp header file. I noticed this when I was
looking at how I can remove the dependncies in is_incrementable.hpp on
the deprecated Type_traits header files in Version2 of type_traits. The
bug looks totally obvious to me. It's that the is_postfix_incrementable
metafunction is derived from the is_incrementable_::impl<T>
implementation rather than the is_incrementable_::postfix_impl<T>
implementation. I am sure this was just a copy-paste problem but
evidently has been in the header file from the beginning.
Can we fast forward the simple fix to the new release ? I posted this
just to be sure I haven't missed anything in the file.
I believe that only the iterator library currently uses the
is_incrementable and is_postfix_incrementable metafunctions in its
tests. Since it is Boost detail no end-user should be using it. Still we
should have it correct, shouldn't we, in our release ?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk