diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2023-02-21 14:30:47 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-21 14:30:47 +0100 |
| commit | bc24a8f2906203beb69a5477d43d7cda3cfdb4eb (patch) | |
| tree | 544d7acef64c3fc05b99d01b22dedaacf1cb6e1c /var | |
| parent | 33bf1fd033af872d60f3878aaac3318c78ae2719 (diff) | |
| download | spack-bc24a8f2906203beb69a5477d43d7cda3cfdb4eb.tar.gz spack-bc24a8f2906203beb69a5477d43d7cda3cfdb4eb.tar.bz2 spack-bc24a8f2906203beb69a5477d43d7cda3cfdb4eb.tar.xz spack-bc24a8f2906203beb69a5477d43d7cda3cfdb4eb.zip | |
Spec.satisfies should be commutative when strict=False (#35598)
The call:
```
x.satisfies(y[, strict=False])
```
is commutative, and tests non-empty intersection, whereas:
```
x.satsifies(y, strict=True)
```
is not commutative, and tests set-inclusion.
There are 2 fast paths. When strict=False both self and other need to
be concrete, when strict=True we can optimize when other is concrete.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions