From 79e569ed2ba0d7de59956b4d432bc9fafb18d0f5 Mon Sep 17 00:00:00 2001 From: Marijn Suijten Date: Wed, 24 Apr 2024 00:24:58 +0200 Subject: [PATCH] event_queue: Fix broken `blocking_dispatch()` link because of unclosed parenthesis Keeping the link target around is redundant as `rustdoc` already infers this from the link name, after removing the backticks. It uses the call-parenthesis to enforce that the link target is indeed an `fn` (and not some other item). --- wayland-client/src/event_queue.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wayland-client/src/event_queue.rs b/wayland-client/src/event_queue.rs index f3878cf89c7..03c119290ee 100644 --- a/wayland-client/src/event_queue.rs +++ b/wayland-client/src/event_queue.rs @@ -249,7 +249,7 @@ impl std::fmt::Debug for QueueEvent { /// In a case where you app is multithreaded and you want to process events in multiple thread, a simple /// pattern is to have one [`EventQueue`] per thread processing Wayland events. /// -/// With this pattern, each thread can use [`EventQueue::blocking_dispatch()`](EventQueue::blocking_dispatch +/// With this pattern, each thread can use [`EventQueue::blocking_dispatch()`] /// on its own event loop, and everything will "Just Work". /// /// ### Single-queue guest library