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
{{ message }}
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
one of the differences between a system like anchors/incremental/adapton and things more like noria is that noria has some notion of an 'upquery'. nodes can pass some request to their dependencies (i want the first 10 rows matching this definition), and that query can be modified based on which children
right now our demand info is basically a bool. i wonder if we could modify this system to have statically typed demand types that flow backwards on the graph? or could this be modelled with fn calls?? seems like the current system might not be generic enough to do this, but maybe i'm just not thinking about the problem in the right way.
this whole thing is extremely similar to our Dict type or IncrMap or raph's rope persistent rope stuff, but where maps and filters on those objects can upquery demand information
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
one of the differences between a system like anchors/incremental/adapton and things more like noria is that noria has some notion of an 'upquery'. nodes can pass some request to their dependencies (i want the first 10 rows matching this definition), and that query can be modified based on which children
right now our demand info is basically a bool. i wonder if we could modify this system to have statically typed demand types that flow backwards on the graph? or could this be modelled with fn calls?? seems like the current system might not be generic enough to do this, but maybe i'm just not thinking about the problem in the right way.
this whole thing is extremely similar to our
Dict
type orIncrMap
or raph's rope persistent rope stuff, but where maps and filters on those objects can upquery demand informationThe text was updated successfully, but these errors were encountered: