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
Currently Traversable and all collection APIs use int for indexes and lengths, so the behavior of these collections when the number of elements exceeds 2147483647 is undefined.
We can’t be constrained by this forever. Since the Foreign Memory API has been delivered, we can easily manage large memory segments exceeding the Integer.MAX_VALUE limit. I think it's time to move away from int and towards long.
Making this change would require modifying a lot of APIs, so we're not in a rush to do it. Here are some of the APIs that will be affected:
AnyTraversable and its subtypes (include all collections);
All functional interfaces with indexes (such as IndexedFunction).
I would like to know users' opinions and suggestions on this. (call @ice1000)
The text was updated successfully, but these errors were encountered:
Currently Traversable and all collection APIs use int for indexes and lengths, so the behavior of these collections when the number of elements exceeds
2147483647
is undefined.We can’t be constrained by this forever. Since the Foreign Memory API has been delivered, we can easily manage large memory segments exceeding the
Integer.MAX_VALUE
limit. I think it's time to move away from int and towards long.Making this change would require modifying a lot of APIs, so we're not in a rush to do it. Here are some of the APIs that will be affected:
AnyTraversable
and its subtypes (include all collections);IndexedFunction
).I would like to know users' opinions and suggestions on this. (call @ice1000)
The text was updated successfully, but these errors were encountered: