Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add test file
simple_signal2.test.ts
, which shows that my current w…
…ay of traversing in `Context.fireUpdateCycle` and `Context.propagateSignalUpdate` are not ordered topologically. - expected traversal: A, B, D, G, C, E, H, F, I, J - actual traversal: A, B, D, G, C, E, H,I, J, F - reason: F gets skipped in the middle because it is already visited once from either B or D, but its resolution is delayed because of unvisited dependencies C and E. however, when C and E are visited, they propagate forward to H and then I. in I's perspective, F has been resolved, since it has been visited. however, the reality is that while it has been visited, it was awaiting dependency resolution of C and E, and it hasn't been resolved yet. the forward propagation model is indeed problematic. you should either stick backward resolution or forward propagation, but not both at the same time.
- Loading branch information