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
In the v53.0.0 release, the Repository.ID is defined as an int64, but there are several consumers are presently defined as int.
For most users this isn't a huge problem, but if you're running on a 32 bit system it will be an issue & also requires an explicit cast when one shouldn't be needed.
I believe we need to standardize on 64 bits for all IDs.
I don't understand why you say this will be a problem on 32 bit systems.
The real problem is if GitHub ever uses a repo ID that doesn't fit in a 32 bit integer, and should not affect which architecture this code is running on, so I believe this is a very low priority issue. That is, unless you can show me otherwise.
In the v53.0.0 release, the Repository.ID is defined as an
int64
, but there are several consumers are presently defined asint
.For most users this isn't a huge problem, but if you're running on a 32 bit system it will be an issue & also requires an explicit cast when one shouldn't be needed.
Affected methods:
The text was updated successfully, but these errors were encountered: