Missing in memory increment about long.js HOT 4 CLOSED

Longs are meant to be immutable. For example, there is a cache for small integer values which is likely to become corrupted otherwise.

If you need something like that you should do this by using your own high/low values as a 32 bit integer, eventually putting that back into a new Long, but never assign something to Long#low/high.

from long.js.

Hmm... Totally missed Longs are meant to be immutable. I maybe have to come up with our own implementation of unsigned int64 "sequence id" that does ++.

p.s. Thanks for doing protobuf.js, long.js and bytebuffer.js. It made my life so much easier.

from long.js.

As this came up a couple of times recently, I tested out a couple of ideas in 59a3dbd but only ended up with https://github.com/dcodeIO/long.js/blob/master/src/long.js#L312

from long.js.

Surprise discovery was that that Long.js is immutable. That answered several questions and would have me taking different approach for this problem rather then opening this issue. If feel that if this is not in the documentation it should.

Also, thanks for the somewhat indirect solution but I don't think I should depends on this method as it may get deprecated, understandably.

from long.js.