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
This item() / namedItem() style is very old-school API design. Modern APIs generally use something like ObservableArray for indexed access, or maplike<> for named access.
I admit we don't seem to have any modern pattern for both named and indexed access. But is that really important? In particular, I'd be surprised if indexed access was important for many use cases. (And it can be emulated, by maplike.values().drop(i).next().value, if it's really needed. At least once iterator helpers lands.)
The text was updated successfully, but these errors were encountered:
This
item()
/namedItem()
style is very old-school API design. Modern APIs generally use something likeObservableArray
for indexed access, ormaplike<>
for named access.I admit we don't seem to have any modern pattern for both named and indexed access. But is that really important? In particular, I'd be surprised if indexed access was important for many use cases. (And it can be emulated, by
maplike.values().drop(i).next().value
, if it's really needed. At least once iterator helpers lands.)The text was updated successfully, but these errors were encountered: