From bcbddf87192f7e3cd159b37c85c9da019b637857 Mon Sep 17 00:00:00 2001 From: Carter Anderson Date: Wed, 15 Apr 2020 12:01:07 -0700 Subject: [PATCH] tweaks --- bevy_wgpu/src/wgpu_resources.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bevy_wgpu/src/wgpu_resources.rs b/bevy_wgpu/src/wgpu_resources.rs index 9047c96dce..8baf0b2ea5 100644 --- a/bevy_wgpu/src/wgpu_resources.rs +++ b/bevy_wgpu/src/wgpu_resources.rs @@ -27,7 +27,7 @@ pub struct WgpuBindGroupInfo { /// /// This is only a problem because RwLockReadGuard.read() erases the guard's lifetime and creates a new anonymous lifetime. If /// you call RwLockReadGuard.read() during a pass, the reference will have an anonymous lifetime that lives for less than the -/// pass. +/// pass, which violates the lifetime constraints in place. /// /// The biggest implication of this design (other than the additional boilerplate here) is that beginning a render pass /// blocks writes to these resources. This means that if the pass attempts to write any resource, a deadlock will occur. WgpuResourceRefs