Fix doc links

Author: madsmtm

objc2/src/foundation/__ns_string.rs

@@ -305,7 +305,7 @@ impl CachedNSString {
 /// Because of that, this should be preferred over [`NSString::from_str`]
 /// where possible.
 ///
-/// [`NSString::from_str`]: crate::NSString::from_str
+/// [`NSString::from_str`]: crate::foundation::NSString::from_str
 #[macro_export]
 macro_rules! ns_string {
     ($s:expr) => {{

objc2/src/foundation/copying.rs

@@ -21,7 +21,7 @@ pub unsafe trait NSCopying: Message {
     /// `copy` message (and others) does not create a new instance, but
     /// instead just retains the instance).
     ///
-    /// [`NSString`]: crate::NSString
+    /// [`NSString`]: crate::foundation::NSString
     type Ownership: Ownership;
 
     /// The output type.

objc2/src/lib.rs

@@ -75,7 +75,7 @@
 //! other type, and this would trigger undefined behaviour!
 //!
 //! Making the ergonomics better is something that is currently being worked
-//! on, the [`objc2::foundation`] module contains more ergonomic usage of at
+//! on, the [`foundation`] module contains more ergonomic usage of at
 //! least parts of the `Foundation` framework.
 //!
 //! Anyhow, all of this `unsafe` nicely leads us to another feature that this
@@ -85,6 +85,7 @@
 //! [`runtime::Object`]: crate::runtime::Object
 //! [`rc::Owned`]: crate::rc::Owned
 //! [`rc::Id`]: crate::rc::Id
+//! [`foundation`]: crate::foundation
 //!
 //!
 //! ## Encodings and message type verification

objc2/src/macros/declare_class.rs

@@ -235,7 +235,7 @@ macro_rules! __inner_declare_class {
 /// Declare a new Objective-C class.
 ///
 /// This is mostly just a convenience macro on top of [`extern_class!`] and
-/// the functionality in the [`objc2::declare`] module, but it can really help
+/// the functionality in the [`declare`] module, but it can really help
 /// with cutting down on boilerplate, in particular when defining delegate
 /// classes!
 ///
@@ -250,7 +250,7 @@ macro_rules! __inner_declare_class {
 ///
 /// The class definition works a lot like [`extern_class!`], with the added
 /// functionality that you can define custom instance variables on your class,
-/// which are then wrapped in a [`objc2::runtime::Ivar`] and made accessible
+/// which are then wrapped in a [`declare::Ivar`] and made accessible
 /// through the class. (E.g. you can use `self.my_ivar` as if it was a normal
 /// Rust struct).
 ///
@@ -277,10 +277,11 @@ macro_rules! __inner_declare_class {
 /// A transformation step is performed on the functions (to make them have the
 /// correct ABI) and hence they shouldn't really be called manually. (You
 /// can't mark them as `pub` for the same reason). Instead, define a new
-/// function that calls it via. [`objc2::msg_send!`].
+/// function that calls it via. [`msg_send!`].
 ///
 /// ["associated functions"]: https://doc.rust-lang.org/reference/items/associated-items.html#methods
 /// ["methods"]: https://doc.rust-lang.org/reference/items/associated-items.html#methods
+/// [`msg_send!`]: crate::msg_send
 ///
 ///
 /// ## Protocol definition
@@ -456,6 +457,8 @@ macro_rules! __inner_declare_class {
 /// ```
 ///
 /// [`extern_class!`]: crate::extern_class
+/// [`declare`]: crate::declare
+/// [`declare::Ivar`]: crate::declare::Ivar
 #[doc(alias = "@interface")]
 #[doc(alias = "@implementation")]
 #[macro_export]

objc2/src/macros/extern_class.rs

@@ -3,24 +3,26 @@
 /// This is similar to an `@interface` declaration in Objective-C.
 ///
 /// The given struct name should correspond to a valid Objective-C class,
-/// whose instances have the encoding [`objc2::Encoding::Object`].
-/// (as an example: `NSAutoreleasePool` does not have this!)
+/// whose instances have the encoding [`Encoding::Object`]. (as an example:
+/// `NSAutoreleasePool` does not have this!)
 ///
 /// You must specify the superclass of this class, similar to how you would
 /// in Objective-C. Due to Rust trait limitations, specifying e.g. the
 /// superclass `NSData` would not give you easy access to `NSObject`'s
 /// functionality, therefore you may specify additional parts of the
 /// inheritance chain.
 ///
+/// [`Encoding::Object`]: crate::Encoding::Object
+///
 ///
 /// # Specification
 ///
 /// This creates an opaque struct containing the superclass (which means that
 /// auto traits are inherited from the superclass), and implements the
 /// following traits for it to allow easier usage as an Objective-C object:
 ///
-/// - [`objc2::RefEncode`]
-/// - [`objc2::Message`]
+/// - [`RefEncode`][crate::RefEncode]
+/// - [`Message`][crate::Message]
 /// - [`Deref<Target = $superclass>`][core::ops::Deref]
 /// - [`DerefMut`][core::ops::DerefMut]
 /// - [`AsRef<$inheritance_chain>`][AsRef]
@@ -33,19 +35,22 @@
 /// `class!(MyObject)`.
 ///
 /// The macro allows specifying fields on the struct, but _only_ zero-sized
-/// types like [`PhantomData`] and [`objc2::declare::Ivar`] are allowed here!
+/// types like [`PhantomData`] and [`declare::Ivar`] are allowed here!
 ///
 /// [`PhantomData`]: core::marker::PhantomData
+/// [`declare::Ivar`]: crate::declare::Ivar
 ///
 ///
 /// # Safety
 ///
 /// The specified superclass must be correct. The object must also respond to
-/// standard memory management messages (this is upheld if `NSObject` is part
-/// of its inheritance chain).
+/// standard memory management messages (this is upheld if [`NSObject`] is
+/// part of its inheritance chain).
 ///
 /// Additionally, any fields (if specified) must be zero-sized.
 ///
+/// [`NSObject`]: crate::foundation::NSObject
+///
 ///
 /// # Example
 ///