how to append a bigint number just like 33383002443812481

[sunyaf]

our user_id is very big , number type is bigint,like 33383002443812481
when i excutor
R.APPENDINTARRAY test 33383002443812481
i get is R.GETINTARRAY test result is 4063432321

[aviggiano]

Hello @sunyaf thank you for the bug report.

Indeed I believe this is being caused by an integer overflow, since 33383002443812481 % 2^32 = 4063432321

I'll look into this and see if this limitation can be removed, otherwise I'll update the documentation to be explicit about this.

[sunyaf]

thank you，it would be soon to be happy.
because i will use it as soon as possible.
it would be very helpful to me.
thank you very much.

[sunyaf]

Hello @sunyaf thank you for the bug report.

Indeed I believe this is being caused by an integer overflow, since 33383002443812481 % 2^32 = 4063432321

I'll look into this and see if this limitation can be removed, otherwise I'll update the documentation to be explicit about this.
thank you，it would be soon to be happy.
because i will use it as soon as possible.
it would be very helpful to me.
thank you very much.

[aviggiano]

Hello

I have confirmed that this issue is due to R.APPENDINTARRAY using internally (1, 2) 32-bit integer arrays, which is the default implementation of the CRoaring build.

From a quick look on their repo it seems that it is possible to create a 64-bit version of the library for C++, but I didn't find anything for C specifically, which could put us in trouble.

In any case, I think this issue won't be very easy to fix.
I'll probably just update the README for now to make it clearer that integers are capped at 32-bits.

I'll keep you updated.

[aviggiano]

Update: I have confirmed that CRoaring do not support 64-bit integers: RoaringBitmap/CRoaring#232, RoaringBitmap/CRoaring#1

We'll have to monitor their progress, so there isn't much we can do on this front for now.
I'll update the README.

[sunyaf]

i find this
`
#include
#include "roaring.hh"
#include "roaring.c"
int main() {
Roaring r1;
for (uint32_t i = 100; i < 1000; i++) {
r1.add(i);
}
std::cout << "cardinality = " << r1.cardinality() << std::endl;

Roaring64Map r2;
for (uint64_t i = 18000000000000000100ull; i < 18000000000000001000ull; i++) {
r2.add(i);
}
std::cout << "cardinality = " << r2.cardinality() << std::endl;
return 0;
}
`
https://github.com/RoaringBitmap/CRoaring
you can search 'Roaring64Map'

[lemire]

The C library is 32-bit only but there is a 64-bit extension in C++.

[sunyaf]

i find this
`
#include
#include "roaring.hh"
#include "roaring.c"
int main() {
Roaring r1;
for (uint32_t i = 100; i < 1000; i++) {
r1.add(i);
}
std::cout << "cardinality = " << r1.cardinality() << std::endl;

Roaring64Map r2;
for (uint64_t i = 18000000000000000100ull; i < 18000000000000001000ull; i++) {
r2.add(i);
}
std::cout << "cardinality = " << r2.cardinality() << std::endl;
return 0;
}
`
https://github.com/RoaringBitmap/CRoaring
you can search 'Roaring64Map'

Requirements

• The library should build on a Linux-like operating system (including MacOS).
• We also support Microsoft Visual studio.
• Though most reasonable processors should be supported, we expect a recent Intel processor: Haswell (2013) or better but support all x64/x86 processors. The library builds without problem on ARM processors.
• Recent C compiler supporting the C11 standard (GCC 4.8 or better or clang), there is also an optional C++ class that requires a C++ compiler supporting the C++11 standard.
• CMake (to contribute to the project, users can rely on amalgamation/unity builds).
• clang-format (optional).
• Serialization on big endian hardware may not be compatible with serialization on little endian hardware.

[sunyaf]

I think C can code with C++