Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
internal/core/adt: fix task completion across disjunction boundaries
This change prevents resolver tasks from triggering evaluating disjunctions of the same node. This change fixes some issue with equality checking that broke code in such scenarios. To complete a task associated with a particular node, one often must also complete the nodes it depends on. This may cause a task, like a resolving task, to trigger the running of a disjunction task. This, in turn, makes it complicated to set up notification to have conjuncts put in the right nodes. But to avoid this complexity altogether, it ensures that completeNodeTasks is not called during the running of a task. Instead, it marks a node needing completion after a task is completed. Note that this change only addresses some of the cases that were necessary to make things run. Further investigation is needed to tighten up this construction. Note that most test changes are difference in error line reporting and reorderings. Other than that this fixes some tests. Issue #2884 Signed-off-by: Marcel van Lohuizen <mpvl@gmail.com> Change-Id: Idcdaab58ef27c29b47f822b668eb53e6c816980c Reviewed-on: https://review.gerrithub.io/c/cue-lang/cue/+/1191586 TryBot-Result: CUEcueckoo <cueckoo@cuelang.org> Unity-Result: CUE porcuepine <cue.porcuepine@gmail.com> Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
- Loading branch information
Showing
22 changed files
with
335 additions
and
380 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.