@@ -10,8 +10,8 @@ use crate::{RclrsError, ToResult};
10
10
/// This is locked whenever initializing or dropping any middleware entity
11
11
/// because we have found issues in RCL and some RMW implementations that
12
12
/// make it unsafe to simultaneously initialize and/or drop middleware
13
- /// entities such as [ `rcl_context_t`] and [ `rcl_node_t`] as well middleware
14
- /// primitives such as [ `rcl_publisher_t`], [ `rcl_subscription_t`] , etc.
13
+ /// entities such as `rcl_context_t` and `rcl_node_t` as well middleware
14
+ /// primitives such as `rcl_publisher_t`, `rcl_subscription_t`, etc.
15
15
/// It seems these C and C++ based libraries will regularly use
16
16
/// unprotected global variables in their object initialization and cleanup.
17
17
///
@@ -59,10 +59,10 @@ pub struct Context {
59
59
pub ( crate ) handle : Arc < ContextHandle > ,
60
60
}
61
61
62
- /// This struct manages the lifetime and access to the [ `rcl_context_t`] . It will also
62
+ /// This struct manages the lifetime and access to the `rcl_context_t`. It will also
63
63
/// account for the lifetimes of any dependencies, if we need to add
64
64
/// dependencies in the future (currently there are none). It is not strictly
65
- /// necessary to decompose [ `Context`] and [ `ContextHandle`] like this, but we are
65
+ /// necessary to decompose `Context` and `ContextHandle` like this, but we are
66
66
/// doing it to be consistent with the lifecycle management of other rcl
67
67
/// bindings in this library.
68
68
pub ( crate ) struct ContextHandle {
0 commit comments