On Sat, 11 May 2019 at 00:55, Jonathan Wakely wrote:
>
> On 11/05/19 00:51 +0300, Ville Voutilainen wrote:
> >On Sat, 11 May 2019 at 00:42, Jonathan Wakely wrote:
> >>
> >> A disabled specialization should not be callable, so move the function
> >> call operator into a new base class which
On 11/05/19 00:51 +0300, Ville Voutilainen wrote:
On Sat, 11 May 2019 at 00:42, Jonathan Wakely wrote:
A disabled specialization should not be callable, so move the function
call operator into a new base class which correctly implements the
disabled hash semantics. For the versioned namespace
On Sat, 11 May 2019 at 00:42, Jonathan Wakely wrote:
>
> A disabled specialization should not be callable, so move the function
> call operator into a new base class which correctly implements the
> disabled hash semantics. For the versioned namespace configuration do
> not derive from
A disabled specialization should not be callable, so move the function
call operator into a new base class which correctly implements the
disabled hash semantics. For the versioned namespace configuration do
not derive from __poison_hash in the enabled case, as the empty base
class serves no
