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
Is your feature request related to a problem? Please describe.
In many cases the code uses UtAssert_UINT32_EQ to check values that are actually size_t in the implementation. This is mostly OK as long as the sizes are <4GiB, which is almost always the case on flight systems that usually don't have a lot of memory.
Describe the solution you'd like
To support larger systems in the future, UT assert should have a macro that compares size_t values natively without converting down to uint32 first.
Describe alternatives you've considered
Continue using uint32 comparisons, accept limitation that this cannot be used for objects/sizes greater than 4GiB.
Additional context
Intent is to be proactive, this will probably become a limiting factor to somebody at some point. Plus it is more correct to be able to compare size_t values in a type-safe manner.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In many cases the code uses
UtAssert_UINT32_EQ
to check values that are actuallysize_t
in the implementation. This is mostly OK as long as the sizes are <4GiB, which is almost always the case on flight systems that usually don't have a lot of memory.Describe the solution you'd like
To support larger systems in the future, UT assert should have a macro that compares
size_t
values natively without converting down touint32
first.Describe alternatives you've considered
Continue using
uint32
comparisons, accept limitation that this cannot be used for objects/sizes greater than 4GiB.Additional context
Intent is to be proactive, this will probably become a limiting factor to somebody at some point. Plus it is more correct to be able to compare
size_t
values in a type-safe manner.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: