Jim Blandy

@cwfitzgerald: > I should have perseved that comment somehow. Ahh, yes, I was reviewing by checking out the branch and just wandering around with rust-analyzer, so I didn't notice that...

So I guess the remaining question is what you think of [this one](https://github.com/gfx-rs/wgpu/pull/5681#issuecomment-2118327977).

So here's the latest version of my suggestion: https://github.com/jimblandy/wgpu/compare/hal-vk-wait-semaphore-is-option%7E2...jimblandy:wgpu:hal-vk-wait-semaphore-is-option

I still want to get a handle on the swapchain semaphores. I've got some work-in-progress docs for those too. I'll take care of this tomorrow morning.

@cwfitzgerald I just pushed two doc commits. Could you look them over for accuracy?

rebased on current trunk

Since I indulged in a rant: There is at least one case where `for_each` makes sense: at the end of a long chain of iterator adaptors. In that case, a...

Could you pull out from those stacks the locks each thread is holding, if any?

Actually, it might suffice simply to know which lock each thread is trying to acquire, and I could figure out which other ones it must be holding.

@cryscan Thanks for the bug report and the analysis! Do the issues you linked (#3518, #3498) exhibit the same behavior on your system? It is extremely valuable for us to...