Audit API usage of int32_t

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: API
    • 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.

              Assignee:
              Unassigned
              Reporter:
              Andrew Morrow (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: