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
The concept of a "transaction" models a sort of fork of the universe, where a (potentially asynchronous) series of writes and reads occurs before "committing" the writes to the main signal graph. Transactions are important for modeling React Suspense-style transitions, and things get especially complicated when multiple transactions can be pending at once (but may be committed separately). We haven't even worked out exactly what the semantics or should be, but @shaylew and @trueadm have been investigating/prototyping in this area. One important result to look for: whether transactions can be modeled on simpler signal primitives, or need built-in support to work well.
The text was updated successfully, but these errors were encountered:
The concept of a "transaction" models a sort of fork of the universe, where a (potentially asynchronous) series of writes and reads occurs before "committing" the writes to the main signal graph. Transactions are important for modeling React Suspense-style transitions, and things get especially complicated when multiple transactions can be pending at once (but may be committed separately). We haven't even worked out exactly what the semantics or should be, but @shaylew and @trueadm have been investigating/prototyping in this area. One important result to look for: whether transactions can be modeled on simpler signal primitives, or need built-in support to work well.
The text was updated successfully, but these errors were encountered: