summaryrefslogtreecommitdiff
path: root/.github/actions/add-maintainers-as-reviewers/Dockerfile
diff options
context:
space:
mode:
authorTodd Gamblin <tgamblin@llnl.gov>2020-12-16 00:57:03 -0800
committerTodd Gamblin <tgamblin@llnl.gov>2020-12-20 07:00:46 -0800
commitbb78a73ed33e24d3b24893c83c6cd77294fe04c7 (patch)
tree5c3656c2af9a8dd1026da2086d3778226814d990 /.github/actions/add-maintainers-as-reviewers/Dockerfile
parentd7fe2d56784d95c471689ca2c524580b76bbe5b0 (diff)
downloadspack-bb78a73ed33e24d3b24893c83c6cd77294fe04c7.tar.gz
spack-bb78a73ed33e24d3b24893c83c6cd77294fe04c7.tar.bz2
spack-bb78a73ed33e24d3b24893c83c6cd77294fe04c7.tar.xz
spack-bb78a73ed33e24d3b24893c83c6cd77294fe04c7.zip
concretizer: move conditional dependency logic into `concretize.lp`
Continuing to convert everything in `asp.py` into facts, make the generation of ground rules for conditional dependencies use facts, and move the semantics into `concretize.lp`. This is probably the most complex logic in Spack, as dependencies can be conditional on anything, and we need conditional ASP rules to accumulate and map all the dependency conditions to spec attributes. The logic looks complicated, but essentially it accumulates any constraints associated with particular conditions into a fact associated with the condition by id. Then, if *any* condition id's fact is True, we trigger the dependency. This simplifies the way `declared_dependency()` works -- the dependency is now declared regardless of whether it is conditional, and the conditions are handled by `dependency_condition()` facts.
Diffstat (limited to '.github/actions/add-maintainers-as-reviewers/Dockerfile')
0 files changed, 0 insertions, 0 deletions