diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-09-23 18:13:53 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-23 18:13:53 +0200 |
| commit | 64e81e5cb7f8a09e22cd1f570f6a6deb6bda4373 (patch) | |
| tree | 060c0a717b9513fd83fea6d21fccd07f8da17497 /compiler/rustc_expand | |
| parent | 8f11c4dadb9e240815ca25e613b17656ab665eda (diff) | |
| parent | 389a502ade65e82d8a0c4d323118121c1c09c4f8 (diff) | |
| download | rust-64e81e5cb7f8a09e22cd1f570f6a6deb6bda4373.tar.gz rust-64e81e5cb7f8a09e22cd1f570f6a6deb6bda4373.zip | |
Rollup merge of #146799 - cuviper:dangling-count-latch, r=lcnr
Fix a dangling reference in `rustc_thread_pool` This diverged from `rayon` in rust-lang/rust#142384, where a cleanup commit turned the matched `worker_index` into a reference, which is read _after_ the `set` that may kill it. I've moved that read beforehand, and I hope the new comments will emphasize the subtlety of this unsafe code. Hopefully fixes rust-lang/rust#146677.
Diffstat (limited to 'compiler/rustc_expand')
0 files changed, 0 insertions, 0 deletions