catch2 has some range matchers like RangeEquals. however i'm running into the following problem:
my underlying type is not ostreamable
view_interface provides operator<< unless IO is explicitly disabled via RANGES_V3_DISABLE_IO
catch2's range matchers will try to stringify the range via operator<<
as a workaround i can compile my unit tests with RANGES_V3_DISABLE_IO, but i wonder if view_interface::operator<< can be enabled only if the underlying type supports operator<<?
catch2 has some range matchers like
RangeEquals. however i'm running into the following problem:view_interfaceprovidesoperator<<unless IO is explicitly disabled viaRANGES_V3_DISABLE_IOoperator<<as a workaround i can compile my unit tests with
RANGES_V3_DISABLE_IO, but i wonder ifview_interface::operator<<can be enabled only if the underlying type supportsoperator<<?