Skip to content

progressively compute view value #28

@pgte

Description

@pgte

Current state

Currently, the view value (Type.value(state)) is re-computed every time, and this has at least a O(n) complexity.
An application typically listens to state changed events and then calls .value(state), which is expensive to do every time there is a mutation.

Proposed solution

Instead of computing the state every time .value() is called, keep the value around and, on each delta applied, change the value accordingly.

This will most probably require some changes to the API, or some new API that makes it stateful and where a specific type can interpret the deltas, generate specific mutation events, and apply them to the view value.

/cc @satazor @jimpick

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions