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 type system doesn't have a way to track the relationship between the first numeric property of a tuple and the behavior of shift (especially when shift changes the contents of the containing array), and I don't think doing so is very realistic.
Daniel Rosenwasser (@DanielRosenwasser) understood, thanks. What about making slice work, since it copies and you could infer types based on each resulting index?
Activity
yulianovdey commentedon Jul 21, 2016
I guess the problem is I'm not supposed to be modifying my "immutable" tuple ;).
DanielRosenwasser commentedon Jul 21, 2016
The type system doesn't have a way to track the relationship between the first numeric property of a tuple and the behavior of
shift(especially whenshiftchanges the contents of the containing array), and I don't think doing so is very realistic.yulianovdey commentedon Jul 21, 2016
Daniel Rosenwasser (@DanielRosenwasser) understood, thanks. What about making
slicework, since it copies and you could infer types based on each resulting index?