Fix broken macro doc links (#27125)
These don't resolve correctly in Rust 1.63.
This commit is contained in:
parent
b2002177be
commit
dce99f1d0d
|
@ -48,6 +48,9 @@ pub const NON_DUP_MARKER: u8 = u8::MAX;
|
||||||
/// It also sets up a [global allocator] and [panic handler], using the
|
/// It also sets up a [global allocator] and [panic handler], using the
|
||||||
/// [`custom_heap_default`] and [`custom_panic_default`] macros.
|
/// [`custom_heap_default`] and [`custom_panic_default`] macros.
|
||||||
///
|
///
|
||||||
|
/// [`custom_heap_default`]: crate::custom_heap_default
|
||||||
|
/// [`custom_panic_default`]: crate::custom_panic_default
|
||||||
|
///
|
||||||
/// [global allocator]: https://doc.rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html
|
/// [global allocator]: https://doc.rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html
|
||||||
/// [panic handler]: https://doc.rust-lang.org/nomicon/panic-handler.html
|
/// [panic handler]: https://doc.rust-lang.org/nomicon/panic-handler.html
|
||||||
///
|
///
|
||||||
|
|
|
@ -7,7 +7,7 @@
|
||||||
//! The most common way to emit logs is through the [`msg!`] macro, which logs
|
//! The most common way to emit logs is through the [`msg!`] macro, which logs
|
||||||
//! simple strings, as well as [formatted strings][fs].
|
//! simple strings, as well as [formatted strings][fs].
|
||||||
//!
|
//!
|
||||||
//! [`msg!`]: msg
|
//! [`msg!`]: crate::msg!
|
||||||
//! [fs]: https://doc.rust-lang.org/std/fmt/
|
//! [fs]: https://doc.rust-lang.org/std/fmt/
|
||||||
//!
|
//!
|
||||||
//! Logs can be viewed in multiple ways:
|
//! Logs can be viewed in multiple ways:
|
||||||
|
|
|
@ -24,6 +24,8 @@ use crate::{
|
||||||
/// program, and provided by _its_ caller. The same is true of the program ID of
|
/// program, and provided by _its_ caller. The same is true of the program ID of
|
||||||
/// the called program.
|
/// the called program.
|
||||||
///
|
///
|
||||||
|
/// [entrypoint!]: crate::entrypoint!
|
||||||
|
///
|
||||||
/// The `Instruction` is usually built from within the calling program, but may
|
/// The `Instruction` is usually built from within the calling program, but may
|
||||||
/// be deserialized from an external source.
|
/// be deserialized from an external source.
|
||||||
///
|
///
|
||||||
|
|
Loading…
Reference in New Issue