On Tue, Feb 06, 2018 at 07:18:47PM +0100, Phil Sutter wrote:
> Automatic merging of adjacent/overlapping ranges upon insertion has
> clear benefits performance- and readability-wise. The drawbacks which
> led to disabling it by default don't apply to anonymous sets since they
> are read-only anyway
Hi Pablo,
On Wed, Feb 07, 2018 at 12:39:43AM +0100, Pablo Neira Ayuso wrote:
> On Tue, Feb 06, 2018 at 07:18:47PM +0100, Phil Sutter wrote:
> > Automatic merging of adjacent/overlapping ranges upon insertion has
> > clear benefits performance- and readability-wise. The drawbacks which
> > led to d
On Wed, 7 Feb 2018, Pablo Neira Ayuso wrote:
> On Tue, Feb 06, 2018 at 07:18:47PM +0100, Phil Sutter wrote:
> > Automatic merging of adjacent/overlapping ranges upon insertion has
> > clear benefits performance- and readability-wise. The drawbacks which
> > led to disabling it by default don't app
Hi Phil,
On Tue, Feb 06, 2018 at 07:18:47PM +0100, Phil Sutter wrote:
> Automatic merging of adjacent/overlapping ranges upon insertion has
> clear benefits performance- and readability-wise. The drawbacks which
> led to disabling it by default don't apply to anonymous sets since they
> are read-o
Automatic merging of adjacent/overlapping ranges upon insertion has
clear benefits performance- and readability-wise. The drawbacks which
led to disabling it by default don't apply to anonymous sets since they
are read-only anyway, so enable this feature for them again.
Cc: Jeff Kletsky
Signed-of
