Skip to content

bazel: simplify done channel rendezvous #462

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

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

matttproud
Copy link
Contributor

Simplify the channel rendezvous to instead of using a buffered channel
with an unergonomical ch <- struct{}{} use a defer close(ch)
semantic. This change is within its scope of usage isomorphic.

Simplify the channel rendezvous to instead of using a buffered channel
with an unergonomical `ch <- struct{}{}` use a `defer close(ch)`
semantic.  This change is within its scope of usage isomorphic.
@matttproud matttproud requested a review from achew22 as a code owner March 4, 2021 22:22
@google-cla google-cla bot added the cla: yes label Mar 4, 2021
@achew22
Copy link
Member

achew22 commented Mar 4, 2021

Thanks for sending in the PR! Out of curiosity, why were you reviewing this section of the code?

@matttproud
Copy link
Contributor Author

matttproud commented Mar 5, 2021

Long story short: I found https://github.com/derivita/bazelpackagesdriver, because I had been interested in golang/go#34341.

I did a code study of the implementation of the driver, which sent me here next. I figured that it was using a subprocess to manage interfacing with Bazel, which I confirmed. Was somewhat interested if any creative solution to making the data access more scaleable was found (mediating driver model with Bazel).

I figured some of this information may be relevant for adapting this to Bazel’s big brother.

@achew22 achew22 merged commit bf4736b into bazelbuild:master Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants