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
Array now serves a dual purpose. First and foremost, it is a mutable collection. However, in a much older version of Latitude, arrays served a slightly different purpose: being meaningfully cloneable. pushBack, popBack, pushFront, and popFront are all designed to work correctly even in the presence of arrays which are cloned or from which clones have been made, but the collection methods do not respect this.
Array is a general-purpose mutable collection. This is, for better or worse, it's purpose in Latitude. As such, I suggest defining a new array-like data type (perhaps "Deque"?) which has only the push/pop methods and is designed to behave correctly when cloned.
The text was updated successfully, but these errors were encountered:
Array
now serves a dual purpose. First and foremost, it is a mutable collection. However, in a much older version of Latitude, arrays served a slightly different purpose: being meaningfully cloneable.pushBack
,popBack
,pushFront
, andpopFront
are all designed to work correctly even in the presence of arrays which are cloned or from which clones have been made, but the collection methods do not respect this.Array
is a general-purpose mutable collection. This is, for better or worse, it's purpose in Latitude. As such, I suggest defining a new array-like data type (perhaps "Deque"?) which has only the push/pop methods and is designed to behave correctly when cloned.The text was updated successfully, but these errors were encountered: