The MPL version is slower to compile and `BOOST_STATIC_ASSERT` is
already used in some places. So unify that.
This also fixes `Wzero-as-null-pointer-constant` warnings, see https://github.com/boostorg/mpl/pull/75
The recent commit 5777e9944b broke code such as
(*it++).foo(), where the result of dereferencing would be convertible to
the value type but did not provide the members of the value type. To mitigate
this, return a reference to the value instead of a proxy object. This will only
work for non-writable iterators (and it didn't work for writable iterators
before either) because in that case a proxy is needed to be able to intercept
operator=.
Also fix a similar issue with (it++)->foo() by adding operator-> overloads
to the post-increment result proxies.
Added tests for the fixes.
Some (strict) C++03 compilers (e.g. `gcc -std=c++03`) reject
'reference-to-reference' in the template and typedef which described
in CWG DR106 [1].
In such situations, iterator_facade rejects reference type as a value
type and some special iterators will become ill-formed:
the test libs/range/test/join.hpp might be descriptive.
[1] http://www.open-std.org/Jtc1/sc22/wg21/docs/cwg_defects.html#106
Signed-off-by: Kohei Takahashi <flast@flast.jp>
- Update iterator_facade test for #1019
(header change already merged).
- Category of each iterator is reduced to a known category before we try to
find a minimum. Fixes#1517.
- `function_input_iterator` from Dean Michael Berris. Fixes#2893
- Fix typo in `boost/iterator.hpp`. Fixes#3434.
- Always include `add_reference` header in iterator adaptor header.
Did not merge changes for #1427.
[SVN r70709]
either changing assert(...) or BOOST_ASSERT(...) to BOOST_TEST
(in my code only)
or adding "return boost::report_errors();" where it was clearly
missing (and a pure bug, in anyone's code).
or changing BOOST_TEST to BOOST_CHECK where the integer library
was clearly using Boost.Test and not returning report_errors().
[SVN r37063]
