> > This is subjectively horrible and, more objectively, would create
> > longer mangled names and additional RTTI.
> Yeah, it's a neat trick but probably not appropriate to use within the
> standard library.
I understand. I was genuinely curious about whether this would do the trick.
In fact, i
Just out of curiosity: would this also work?
template
struct _Absent {};
template
using __maybe_present_t = __conditional_t<_Present, _Tp, _Absent<_Tp,
_Disc>>;
That would avoid having to type 0, 1, ... manually.
Hi Jonathan
Thanks so much for implementing this.
There are a couple of typos in the patch description:
's/C==17RandomAccessIterator/Cpp17RandomAccessIterator/' and
's/__or_/__and_/'.
I've applied your patch localy and it works fine for all my use cases,
which admitedly simply consist of using v
On Mon, Oct 17, 2022 at 05:32:32AM +0200, Martin Uecker wrote:
> Hm, that already seems to work with
>
> if (!std::isfinite(x))
> __builtin_unreachable();
>
> https://godbolt.org/z/hj3WrEhjb
Not anymore. Perhaps after making ranger the VRP default, because I get the
mentioned outcome with --para