-
Notifications
You must be signed in to change notification settings - Fork 482
Create internal rust_binary rule instead of using transitions #1187
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
Conversation
This seems like a cleaner way to break the dependency that rust_binary has on the process wrapper. The common args are consumed and modified to set the process wrapper to None, which is detected and performs the appropriate switch. The transitions and settings can then be removed.
I can confirm that this fixes some cycles I was seeing when querying the bazel dependency graph after #1159. |
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.
One question but otherwise looks good!
All of those changes look fine to me. I'll be able to get back to this later Sunday night, so feel free to update and merge. I think you should have permission. |
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.
Thanks for working on this!
Thanks! Indeed much simpler! |
This seems like a cleaner way to break the dependency that rust_binary
has on the process wrapper. The common args are consumed and modified
to set the process wrapper to None, which is detected and performs the
appropriate switch. The transitions and settings can then be removed.