-
Notifications
You must be signed in to change notification settings - Fork 1.7k
internal: switch remaining OpQueues to use named structs #18216
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
internal: switch remaining OpQueues to use named structs #18216
Conversation
bors merge |
@bors r+ |
…eykril internal: switch remaining OpQueues to use named structs Building atop of #18195, I switched `GlobalState::fetch_build_data_queue` to use a struct instead of a tuple. (I didn't switch `fetch_proc_macros_queue` to not return a bool, as the return value is only used in one spot.)
☀️ Test successful - checks-actions |
👀 Test was successful, but fast-forwarding failed: 422 Update is not a fast forward |
bc8b860
to
501ef0e
Compare
@bors r+ |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
👀 Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request. |
Building atop of #18195, I switched
GlobalState::fetch_build_data_queue
to use a struct instead of a tuple.(I didn't switch
fetch_proc_macros_queue
to not return a bool, as the return value is only used in one spot.)