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
It seems to be recreating all objects down to the deeper nested path where a transformation occurs. Is that right? Is that the major source of performance concerns?
The recreation of objects down to where transformation occurs is intentional as the idea is to treat data structures as immutable and not to mutate any existing objects. So, yes that is right and there are certainly cases where use of immutable data structures can be a performance concern, but that is not the kind of performance consideration that this issue mostly about.
The idea with this issue is to document kinds of performance considerations where one might not realize that a particular way to use this library might lead to poor performance compared to some other way to use this library. There is already a section on performance tips, but it is not complete.
There should a section in the documentation that explains main performance considerations when using lenses.
L.choose
L.toFunction
to precompute compositionsThe text was updated successfully, but these errors were encountered: