From 8581b9d298e3bfc872a598380a09eb386a9db408 Mon Sep 17 00:00:00 2001 From: Jim Blandy <jimb@red-bean.com> Date: Sun, 1 Oct 2023 18:12:56 -0700 Subject: [PATCH] Fix some broken links in the documentation. --- wayland-backend/src/protocol.rs | 8 ++++++-- wayland-client/src/event_queue.rs | 4 ++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/wayland-backend/src/protocol.rs b/wayland-backend/src/protocol.rs index 0abdbc4c382..6b6b8664f2b 100644 --- a/wayland-backend/src/protocol.rs +++ b/wayland-backend/src/protocol.rs @@ -28,9 +28,11 @@ pub enum ArgumentType { Object(AllowNull), /// Id of a newly created wayland object NewId, - /// Vec<u8> + /// `Vec<u8>` Array, /// A file descriptor argument. Represented by a [`RawFd`]. + /// + /// [`RawFd`]: std::os::fd::RawFd Fd, } @@ -60,12 +62,14 @@ pub enum Argument<Id, Fd> { Object(Id), /// Id of a newly created wayland object NewId(Id), - /// Vec<u8> + /// `Vec<u8>` /// /// The value is boxed to reduce the stack size of Argument. The performance /// impact is negligible as `array` arguments are pretty rare in the protocol. Array(Box<Vec<u8>>), /// A file descriptor argument. Represented by a [`RawFd`]. + /// + /// [`RawFd`]: std::os::fd::RawFd Fd(Fd), } diff --git a/wayland-client/src/event_queue.rs b/wayland-client/src/event_queue.rs index b13238ef460..5507ab9e98d 100644 --- a/wayland-client/src/event_queue.rs +++ b/wayland-client/src/event_queue.rs @@ -31,7 +31,7 @@ use crate::{conn::SyncData, Connection, DispatchError, Proxy}; /// /// In the rare case of an interface with *events* creating new objects (in the core protocol, the only /// instance of this is the `wl_data_device.data_offer` event), you'll need to implement the -/// [`Dispatch::event_created_child()`] method. See the [`event_created_child!`](event_created_child!) macro +/// [`Dispatch::event_created_child()`] method. See the [`event_created_child!`](macro.event_created_child.html) macro /// for a simple way to do this. /// /// ## Modularity @@ -120,7 +120,7 @@ where /// Method used to initialize the user-data of objects created by events /// /// If the interface does not have any such event, you can ignore it. If not, the - /// [`event_created_child!`](event_created_child!) macro is provided for overriding it. + /// [`event_created_child!`](macro.event_created_child.html) macro is provided for overriding it. #[cfg_attr(coverage, coverage(off))] fn event_created_child(opcode: u16, _qhandle: &QueueHandle<State>) -> Arc<dyn ObjectData> { panic!(