You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One use case for the auditor is to better understand the assumptions your code is making. Another is to ensure that you're not making assumptions of specific types (or never introducing more beyond a base set). For the latter case, it would be nice for the auditor to allow failing a build it detects assumptions of a certain type.
To ensure that no new assumptions are added, it may work to check the output of the auditor (maybe the Markdown version) into a repo and then have the CI check that the latest output always matches this initial version.
The text was updated successfully, but these errors were encountered:
One use case for the auditor is to better understand the assumptions your code is making. Another is to ensure that you're not making assumptions of specific types (or never introducing more beyond a base set). For the latter case, it would be nice for the auditor to allow failing a build it detects assumptions of a certain type.
To ensure that no new assumptions are added, it may work to check the output of the auditor (maybe the Markdown version) into a repo and then have the CI check that the latest output always matches this initial version.
The text was updated successfully, but these errors were encountered: