-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Move pattern matching outside of the loop #92177
Move pattern matching outside of the loop #92177
Conversation
This comment has been minimized.
This comment has been minimized.
027e0fa
to
0d33f6d
Compare
I don't feel strongly, but the advantage of matching inside the loop is that the I do like the @bors r+ rollup=iffy (could have small perf effect) |
📌 Commit 0d33f6d has been approved by |
⌛ Testing commit 0d33f6d with merge a2d17b2cf329c30b3c2cb76e224b6ca37af07acb... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
⌛ Testing commit 0d33f6d with merge 0bf68cee7601b0d68dc294d19be0eab33097ecc9... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry There were a bunch of errors during the submodule checkout stage. Those should have errored, I will look into that shortly. |
⌛ Testing commit 0d33f6d with merge 1cfd8a83f570a7953c7813ee76414937b4446009... |
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
☀️ Test successful - checks-actions |
Finished benchmarking commit (489296d): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
…ulacrum Error if submodule fetch fails. In CI, if fetching a submodule fails, the script would exit successfully. Later parts of the build will fail due to the missing files, but it is a bit confusing, and I think it would be better to error out earlier. The reason is that in bash, `wait` without arguments will exit 0 even if a background job exits with an error. The solution here is to wait on each individual job, which will return the exit code of the job. This was encountered in rust-lang#92177.
…acrum Error if submodule fetch fails. In CI, if fetching a submodule fails, the script would exit successfully. Later parts of the build will fail due to the missing files, but it is a bit confusing, and I think it would be better to error out earlier. The reason is that in bash, `wait` without arguments will exit 0 even if a background job exits with an error. The solution here is to wait on each individual job, which will return the exit code of the job. This was encountered in rust-lang#92177.
Not sure if worth it but it's been bugging me for a while now.
r? @camelid