From f94f25f355ba849a5814cf98df6bba86af49b0d1 Mon Sep 17 00:00:00 2001 From: Jim Blandy Date: Thu, 9 Jun 2022 12:44:13 -0700 Subject: [PATCH] Fix documentation links. --- wgpu-core/src/command/bundle.rs | 3 +++ wgpu-core/src/device/life.rs | 2 +- wgpu-core/src/track/mod.rs | 7 ++++--- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/wgpu-core/src/command/bundle.rs b/wgpu-core/src/command/bundle.rs index 85e9d849e0..ca7dc0100d 100644 --- a/wgpu-core/src/command/bundle.rs +++ b/wgpu-core/src/command/bundle.rs @@ -1085,6 +1085,9 @@ struct VertexLimitState { /// [`SetIndexBuffer`] to the simulated state stored here, and then /// calls the `flush_foo` methods before draw calls to produce the /// update commands we actually need. +/// +/// [`SetBindGroup`]: RenderCommand::SetBindGroup +/// [`SetIndexBuffer`]: RenderCommand::SetIndexBuffer struct State { /// Resources used by this bundle. This will become [`RenderBundle::used`]. trackers: RenderBundleScope, diff --git a/wgpu-core/src/device/life.rs b/wgpu-core/src/device/life.rs index 3f8cd6e7cf..87d84633bd 100644 --- a/wgpu-core/src/device/life.rs +++ b/wgpu-core/src/device/life.rs @@ -461,7 +461,7 @@ impl LifetimeTracker { impl LifetimeTracker { /// Identify resources to free, according to `trackers` and `self.suspected_resources`. /// - /// Given `trackers`, the [`TrackerSet`] belonging to same [`Device`] as + /// Given `trackers`, the [`Tracker`] belonging to same [`Device`] as /// `self`, and `hub`, the [`Hub`] to which that `Device` belongs: /// /// Remove from `trackers` each resource mentioned in diff --git a/wgpu-core/src/track/mod.rs b/wgpu-core/src/track/mod.rs index 8d38ff8e72..818c5b96c4 100644 --- a/wgpu-core/src/track/mod.rs +++ b/wgpu-core/src/track/mod.rs @@ -690,9 +690,10 @@ impl Tracker { /// the state given for those resources in the UsageScope. It also /// removes all touched resources from the usage scope. /// - /// If a transition is needed to get the resources into the needed state, - /// those transitions are stored within the tracker. A subsequent - /// call to [`Self::drain`] is needed to get those transitions. + /// If a transition is needed to get the resources into the needed + /// state, those transitions are stored within the tracker. A + /// subsequent call to [`BufferTracker::drain`] or + /// [`TextureTracker::drain`] is needed to get those transitions. /// /// This is a really funky method used by Compute Passes to generate /// barriers after a call to dispatch without needing to iterate