NODE-2624Backlog

BSON Timestamp should wrap its value and present as an unsigned long

{{Timestamp}} extends {{Long}}, so it exposes the whole 64-bit integer API: arithmetic, bitwise ops, signedness, raw {{low}}/{{high}}. A BSON Timestamp is just two uint32s, {{t}} (seconds since epoch) and {{i}} (increment), and most of that API makes no sense for it. It also gives odd results, e.g. {{ts.add(...)}} returns a {{Long}} (NODE-4098). NODE-7069 (bson 7.3.0, js-bson #887) did the groundwork with no runtime changes. It split the inherited {{Long}} members into kept and deprecated (th

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
BSON
Labels
Tags and classification
breakingshell-breakingusability