I noticed since champ_iterator() = default; was removed, immer::map no longer satisfies the constraint std::ranges::range, which prevents usage with views, e.g. for(const auto &v : map | std::views::values).
The issue is with std::ranges::end(), but oddly, std::end() compiles fine. I'm not sure if this is a difference in the standard or a compiler issue.
For reference, I'm compiling on MSVC v19.34.31935 (latest version at present time).
I'm happy to submit a PR to reintroduce the default constructor but wanted to check if this is wanted/the right way to go about it.
I noticed since
champ_iterator() = default;
was removed,immer::map
no longer satisfies the constraintstd::ranges::range
, which prevents usage with views, e.g.for(const auto &v : map | std::views::values)
.The issue is with
std::ranges::end()
, but oddly,std::end()
compiles fine. I'm not sure if this is a difference in the standard or a compiler issue.For reference, I'm compiling on MSVC v19.34.31935 (latest version at present time).
I'm happy to submit a PR to reintroduce the default constructor but wanted to check if this is wanted/the right way to go about it.