Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iterator traits/use std #43

Closed

Conversation

theodelrieu
Copy link

@theodelrieu theodelrieu commented Sep 20, 2021

Using Boost.Move breaks range-v3, since the latter specializes std::iterator_traits for its custom iterators, but does not provide all member type aliases.

See ericniebler/range-v3#1660

Using Boost.Move breaks range-v3, since the latter
specializes std::iterator_traits for its custom iterators.

Note that while C++20 requires std::is_object<T> on the T*
specialization, this breaks some Boost code.
@igaztanaga
Copy link
Member

I could not reproduce the issue with the following test with latest MSVC 2019 andd GCC 10.3 in C++17/20 modes:

#include <range/v3/all.hpp>
#include <boost/container/flat_map.hpp>

int main()
{
   using namespace boost::container;
   auto f = ranges::to< flat_map<int, int> >();
   (void)f;
   return 0;
}`

I'm using Boost 1.78 and Ranges-v3 0.11 and current master. Could you provide a minimal test case and compiler/toolset versions to reproduce the bug?

@igaztanaga
Copy link
Member

Closing the issue due to inactivity.

@igaztanaga igaztanaga closed this Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants