Re: [optional] Feedback on the range interface for Boost.Optional

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2024-09-15 19:25:09

On 9/15/24 20:55, Andrzej Krzemienski via Boost wrote:
> 
> The usages for the interop with ranges were given, but it looks like there
> are no other usages not involving ranges.

I'm not familiar with ranges, but is there an integration layer that
would allow std::/boost::optional plug into the ranges infrastructure
without modification? Some sort of traits that could be specialized or
ADL-found free functions?

For example, we could provide begin()/end() overloads for boost::optional.