equal_range does not work

[GoogleCodeExporter]

equal_range currently returns
pair(pos, pos)
whereas it should return
pair(pos, pos+1)
or
pair(end, end)
if the element was not found.
Since the range returned is open on one side [first, last), [pos, pos) is
the empty set.

Thanks,
Shaun

Original issue reported on code.google.com by sjackman on 8 May 2009 at 5:38

[GoogleCodeExporter]

Crikey!  You're absolutely right.  This has been a bug in sparsehash for 
forever; I
guess not many folks use equal_range since these aren't multi-maps.  Still, 
seems
like a pretty bad bug to have in there.  I'll see about pushing a new release 
this
weekend.

Original comment by csilv...@gmail.com on 8 May 2009 at 8:28

• Changed state: Accepted
• Added labels: Priority-High, Type-Defect

[GoogleCodeExporter]

Great! Thanks, Craig.

Original comment by sjackman on 8 May 2009 at 10:11

[GoogleCodeExporter]

I've just released sparsehash 1.5.1 to fix this bug.

Original comment by csilv...@gmail.com on 9 May 2009 at 4:16

• Changed state: Fixed

[GoogleCodeExporter]

Speedy! Thanks a lot, Craig.

Original comment by sjackman on 9 May 2009 at 4:31