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

Steve Downey wrote:

What sort of changes are you anticipating? Opting out of std::format range formatting was one thing we discovered. Does boost jason have similar things for ranges?

Everything that does automatic range handling will potentially be affected, e.g. hash_value. Yes, Boost.JSON does this as well (provide a default implementation for range- like things.)