Repository navigation
Conversation
Define no-assignment prerequisites as non-matching conditions that allow root fallback evaluation. Environment: Datadog workspace Co-Authored-By: Codex GPT-5 <noreply@localhost>
Exercise both membership operators against one memoized unassigned prerequisite. Environment: Datadog workspace Co-Authored-By: Codex GPT-5 <noreply@localhost>
typotter
marked this pull request as ready for review
October 30, 2026 18:15
typotter
marked this pull request as draft
October 30, 2026 18:17
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Define the distinction between a failed prerequisite and a prerequisite that evaluates successfully but produces no assignment.
A prerequisite returning
DEFAULTwithout a variant makes its dependency condition not match. Evaluation may continue to a later root allocation. Missing flags and evaluation errors still fail the dependency graph.Changes
Decisions
nullvariant.ONE_OFandNOT_ONE_OFconditions treat no assignment as non-matching.Checklist