diff options
author | Todd Gamblin <tgamblin@llnl.gov> | 2017-09-11 11:43:41 -0700 |
---|---|---|
committer | Todd Gamblin <tgamblin@llnl.gov> | 2017-09-11 17:13:21 -0700 |
commit | f8f1c308c994512622c952d289388f9ab7f19709 (patch) | |
tree | cd5eb0bf3cf15437ce122b73c436ded105e77556 /.gitignore | |
parent | 8c42aed9d5f8b02538eb15ac936c78bc6a36308a (diff) | |
download | spack-f8f1c308c994512622c952d289388f9ab7f19709.tar.gz spack-f8f1c308c994512622c952d289388f9ab7f19709.tar.bz2 spack-f8f1c308c994512622c952d289388f9ab7f19709.tar.xz spack-f8f1c308c994512622c952d289388f9ab7f19709.zip |
clean up concreteness detection
- Fixes bugs where concretization would fail due to an erroneously cached
_concrete attribute.
- Ripped out a bunch of code in spec.py that isn't needed/valid anymore:
- The various concrete() methods on different types of Specs would
attempt to statically compute whether the Spec was concrete.
- This dates back to when DAGs were simpler and there were no optional
dependencies. It's actually NOT possible to compute statically
whether a Spec is concrete now. The ONLY way you know is if it goes
through concretization and is marked concrete once that completes.
- This commit removes all simple concreteness checks and relies only on
the _concrete attribute. This should make thinking about
concreteness simpler.
- Fixed a couple places where Specs need to be marked concrete explicitly.
- Specs read from files and Specs that are destructively copied from
concrete Specs now need to be marked concrete explicitly.
- These spots may previously have "worked", but they were brittle and
should be explcitly marked anyway.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions