9 Jun
2013
9 Jun
'13
12:28 p.m.
Yusuke Ichinohe wrote:
I think simpler solution would be to add range support for boost::optional in additional header (e.g.
). i.e. boost::optional will become random access range.
I saw this "container-view of boost::optional" on the Boost ML in the past, but I don't remember what was the conclusion. If you want to make this support added in Boost.Range, I recommend you to start a new thread (with the magic words "Oven range library already has this functionality"). And please don't top-post! ( http://www.boost.org/community/policy.html ) Regards, Michel