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

Extract derive_swift_module_name as a free function in its own .bzl file #1347

Conversation

brentleyjones
Copy link
Collaborator

Since rules may want to use this without the other functionality in swift_common (e.g., compilation), isolating it to its own file can reduce analysis churn when other parts of the rule implementations change.

PiperOrigin-RevId: 493078921
(cherry picked from commit 47bd14c)

…l` file

Since rules may want to use this without the other functionality in `swift_common` (e.g., compilation), isolating it to its own file can reduce analysis churn when other parts of the rule implementations change.

PiperOrigin-RevId: 493078921
(cherry picked from commit 47bd14c)
Signed-off-by: Brentley Jones <github@brentleyjones.com>
brentleyjones referenced this pull request Oct 7, 2024
…l` file.

Since rules may want to use this without the other functionality in `swift_common` (e.g., compilation), isolating it to its own file can reduce analysis churn when other parts of the rule implementations change.

PiperOrigin-RevId: 493078921
@brentleyjones brentleyjones enabled auto-merge (rebase) October 7, 2024 14:09
@brentleyjones brentleyjones merged commit 16a50dc into master Oct 7, 2024
14 checks passed
@brentleyjones brentleyjones deleted the bj/extract-derive_swift_module_name-as-a-free-function-in-its-own-.bzl-file branch October 7, 2024 15:32
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.

3 participants