Boost iterator facade implementation

25 Oct
2018
25 Oct
'18
6:41 p.m.
https://github.com/boostorg/iterator/blob/boost-1.63.0/include/boost/iterato... I was wondering about is_non_proxy_reference<Reference,Value> in this metafunction. It appears to select between postfix_increment_proxy<Iterator> and writable_postfix_increment_proxy<Iterator> based on whether Reference is the same type as Value ignoring cv& what is the case that writable_postfix_increment_proxy<Iterator> is selected. So when is Reference going to be a different 'base type' to Value? is this to support user returning their own proxy or something?
2428
Age (days ago)
2428
Last active (days ago)
0 comments
1 participants
participants (1)
-
rmawatson rmawatson