Doug Gregor 91ddaf59eb Archetype builder: start tracking the locations and reasons for specific requirements. ...

Whenever we add a requirement, we now know

  (1) Why we added the requirement, e.g., whether it was explicitly written, inferred from a signature, or introduced by an outer scope.
  (2) Where in the source code that requirement originated.

Also add a debugging flag for dumping the archetype builder information, so we can write tests against it.

This is effectively NFC, but it's infrastructure to help a number of requirements-related tasks.

Swift SVN r22638

2014-10-09 21:52:28 +00:00

35 KiB

Raw Blame History

View Raw