You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently increment the counter in thread unsafe manner. See comment here related to that. Its good to be more accurate than the current implementation by using a thread-safe way to increment the count.
The current type is a uint32_t, where _InterlockedIncrement doesn't work without a cast in non-Windows and there is a pending request to change the API due to likely overflow of the current data type.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.
Issue Details
We currently increment the counter in thread unsafe manner. See comment here related to that. Its good to be more accurate than the current implementation by using a thread-safe way to increment the count.
The current type is a uint32_t, where _InterlockedIncrement doesn't work without a cast in non-Windows and there is a pending request to change the API due to likely overflow of the current data type.
We currently increment the counter in thread unsafe manner. See comment here related to that. Its good to be more accurate than the current implementation by using a thread-safe way to increment the count.
The current type is a uint32_t, where _InterlockedIncrement doesn't work without a cast in non-Windows and there is a pending request to change the API due to likely overflow of the current data type.
The text was updated successfully, but these errors were encountered: