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
The same field in a model would be uint and in another model int or int64 and there is some conversion here and there. we should agree on specific types and use them always.
another thing, I understand that int64 is/should be big enough, but is there any reason to use it vs unsigned type for things like time interval, resources, and entity ids?
The text was updated successfully, but these errors were encountered:
sameh-farouk
changed the title
Review numeric fields in models, make sure to choose a proper type and to be consistent
Review numeric fields in models, make sure to choose a proper size and to be consistent
Jan 26, 2023
Description
The same field in a model would be uint and in another model int or int64 and there is some conversion here and there. we should agree on specific types and use them always.
another thing, I understand that int64 is/should be big enough, but is there any reason to use it vs unsigned type for things like time interval, resources, and entity ids?
The text was updated successfully, but these errors were encountered: