RoaringBitmap.toString produces large strings which create problems for debuggers

[richardstartin]

The only good way to figure out what container types are used during development is to inspect in memory objects with a debugger, but the string returned by RoaringBitmap.toString is too large for this to be ergonomic, causing IDEs GC problems. This could be fixed with a much smaller string size.

[lemire]

I think that's more of a possible enhancement than a bug, no?

[richardstartin]

The label was added by accident. It’s neither an enhancement nor a bug in my opinion, just a removal of an ergonomic irritation.

[simeonpilgrim]

too much memory, we limit the size

it almost seems like it there on purpose. But perhaps it print too much. I know i was finding if helpful the other day (for very small sets)

ah. My bad the above is from Roaring64Bitmap.

[richardstartin]

There is a limit but it is too high