On 07/11/2018 12:24 PM, Trevor Saunders wrote:
> However if we went that route we should prevent use of the
> assignment operator by declaring one explicitly and making it private but
> then not implementing it, so it at least fails to link and with some
> macros you can actually tell the compiler
On Tue, Jul 10, 2018 at 11:46:54AM +0200, Richard Biener wrote:
> On Tue, 10 Jul 2018, Trevor Saunders wrote:
>
> > On Tue, Jul 10, 2018 at 10:43:20AM +0200, Richard Biener wrote:
> > >
> > > The following makes the hash-map iterator dereference return a pair > > Value&> rather than a copy of Val
On Tue, 10 Jul 2018, Richard Biener wrote:
> On Tue, 10 Jul 2018, Trevor Saunders wrote:
>
> > On Tue, Jul 10, 2018 at 10:43:20AM +0200, Richard Biener wrote:
> > >
> > > The following makes the hash-map iterator dereference return a pair > > Value&> rather than a copy of Value. This matches th
On Tue, 10 Jul 2018, Trevor Saunders wrote:
> On Tue, Jul 10, 2018 at 10:43:20AM +0200, Richard Biener wrote:
> >
> > The following makes the hash-map iterator dereference return a pair > Value&> rather than a copy of Value. This matches the hash-table iterator
> > behavior and avoids issues wit
On Tue, Jul 10, 2018 at 10:43:20AM +0200, Richard Biener wrote:
>
> The following makes the hash-map iterator dereference return a pair Value&> rather than a copy of Value. This matches the hash-table iterator
> behavior and avoids issues with
>
> hash_map >
Eventually somebodies probably goi
The following makes the hash-map iterator dereference return a pair rather than a copy of Value. This matches the hash-table iterator
behavior and avoids issues with
hash_map >
where iterating over the hash-table will call the auto_vec destructor
when dereferencing the iterator. I note that
