new rangeOnfOnes implementation induces multiple test suite failures

[roaringbitmap]

new rangeOnfOnes implementation induces multiple test suite failures

[glycerine]

okay, it was no big deal. The equals() methods weren't checking for container types other than their own. fixed at 9bf6b3e (tip of glycerine/rle branch)

[glycerine]

mmm.... too hasty in closing; there are still some test failures with runContainer16 in place for rangeOfOnes:

Failures:

  * /Users/jaten/go/src/github.com/glycerine/roaring/roaring_test.go 
  Line 787:
  Expected: '96617'
  Actual:   '9'
  (Should be equal)

Failures:

  * /Users/jaten/go/src/github.com/glycerine/roaring/roaring_test.go 
  Line 865:
  Expected: '35392'
  Actual:   '1928'
  (Should be equal)

Failures:

  * /Users/jaten/go/src/github.com/glycerine/roaring/roaring_test.go 
  Line 886:
  Expected: '131999'
  Actual:   '131351'
  (Should be equal)


Failures:

  * /Users/jaten/go/src/github.com/glycerine/roaring/roaring_test.go 
  Line 933:
  Expected: 'true'
  Actual:   'false'
  (Should be equal)


--- FAIL: TestBitmap (12.96s)

Failures:

  * /Users/jaten/go/src/github.com/glycerine/roaring/roaring_test.go 
  Line 1589:
  Expected: 'true'
  Actual:   'false'
  (Should be equal)

--- FAIL: TestFlipBigA (0.12s)

[glycerine]

The Not(range) algorithm was incorrect and untested.
Both these problems are fixed in the latest push to glycerine/rle branch; eb38642