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
Lookup formulas currently correspond to a pet name path of length at least 2, and the value resolved thereby. We should instead create a lookup formula for each path segment, and store a reference to the parent segment formula in each child. Ideally, we should be able to synchronously retrieve existing formulas for a given pet name path, provided that the path is local to the current daemon.
The text was updated successfully, but these errors were encountered:
@kriskowal, I believe we originally planned to derive child segment formula numbers from their parents, but #2089 removed derivation in favor of randomly generating all formula numbers. Can we reintroduce derivation for this purpose? It seems problematic if we're also trying to ensure that formula numbers are never reused.
Fixes: #2021
Progresses: #2086
Ref: #2098
Synchronizes the host's `evaluate()` method by delegating all incarnations to the daemon via `incarnateEval()`. The latter is responsible for incarnating its dependents as necessary, and for the generation of their formula numbers. To facilitate this, the synchronous methods `incarnateLookupSync()` and `incarnateWorkerSync()` have been added. These methods synchronously mutate the formula graph, and return promises that resolve when the formulas have been written to disk. The result is that the formula graph is mutated within a single turn of the event loop.
Lookup formulas currently correspond to a pet name path of length at least 2, and the value resolved thereby. We should instead create a lookup formula for each path segment, and store a reference to the parent segment formula in each child. Ideally, we should be able to synchronously retrieve existing formulas for a given pet name path, provided that the path is local to the current daemon.
The text was updated successfully, but these errors were encountered: