-
Notifications
You must be signed in to change notification settings - Fork 124
Dependencies: validate unused module dependencies #744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependencies: validate unused module dependencies #744
Conversation
@swift-ci test |
I'm going to expand this PR to also allow for optional dependencies. |
@swift-ci test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks OK to me, but it seems like we're piling up a lot of separate settings to control the diagnostics. At some point, we need to figure out a plan to simplify that, e.g., with some overarching setting that sets the defaults for different things.
Yeah, I agree. I think we're thinking of the fine-grained settings as temporary for initial rollout and user testing, to avoid having a universal setting like VALIDATE_DEPENDENCIES / VALIDATE_UNUSED_DEPENDENCIES rapidly change behavior. |
a674b2d
to
f1ba301
Compare
@swift-ci test |
Tests aren't running... @swift-ci test |
@swift-ci test |
rdar://159126103