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
As of #1135 Records are no longer collections.
This is fine when using Records explicitly but makes "reflection" difficult, i.e. how do you iterate over each key? Converting to a Seq each time seems very wasteful.
Examples of when I need this: Zalastax/immutable-devtools@13569c7 and Zalastax/tsdiff@29609cc
The text was updated successfully, but these errors were encountered:
Treating Records as collections is not an API to be encouraged, which is why these functions were removed. For special cases that need to use reflection, converting to Seq is the right decision. Similar to how you might use Object.keys() to reflect on a plain JS Object, rather than assuming that Object to behave like a collection in all cases.
Seq is not wasteful in a performance sense, since it only offers a lazy view over the underlying data - there is very little overhead.
As of #1135 Records are no longer collections.
This is fine when using Records explicitly but makes "reflection" difficult, i.e. how do you iterate over each key? Converting to a Seq each time seems very wasteful.
Examples of when I need this: Zalastax/immutable-devtools@13569c7 and Zalastax/tsdiff@29609cc
The text was updated successfully, but these errors were encountered: