Skip to content
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

Remove swift_usage_aspect and SwiftUsageInfo #1138

Closed
wants to merge 1 commit into from

Conversation

luispadron
Copy link
Contributor

Cherry-picked from commit: c24a84a

With the toolchain information removed, this aspect/provider offers a minimal API.
The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.

luispadron referenced this pull request Nov 17, 2023
…rules_apple.

With the toolchain information removed, this aspect/provider offers a minimal API. The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.

PiperOrigin-RevId: 439577534
@luispadron luispadron marked this pull request as ready for review November 17, 2023 18:07
Cherry-picked from commit: c24a84a

> With the toolchain information removed, this aspect/provider offers a minimal API.
> The only client is rules_apple, which uses it to determine if Swift support may need to be bundled at all, so it's better that that single client own it, rather than rules_swift try to provide an API that could serve all possible hypothetical clients.
@luispadron luispadron marked this pull request as draft November 17, 2023 18:23
@luispadron luispadron closed this May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants