- 
    Type:Task 
- 
    Resolution: Unresolved
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: None
- 
    Component/s: API
- 
    None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
We should review usages of int32_t in the API and ensure that they are correct. In particular, things like pipeline::skip or pipeline::sample. Another example is places where we are specifying a base fixed size integer for enumerations. Is this actually needed? Or should we let it default to int? Changing integer sizes is a common source of ABI breaks so we should make sure we are doing the right thing out of the gate.
- is related to
- 
                    CXX-1338 Capped size in bytes is limited to 32bit integer, need 64bit integer -         
- Closed
 
-         
- related to
- 
                    CDRIVER-1329 maxTimeMS and maxAwaitTimeMS should be Int64, not Int32 -         
- Backlog
 
-