|
1 |
| -//! Panic support for libcore |
| 1 | +//! Panic support for core |
2 | 2 | //!
|
3 | 3 | //! The core library cannot define panicking, but it does *declare* panicking. This
|
4 |
| -//! means that the functions inside of libcore are allowed to panic, but to be |
5 |
| -//! useful an upstream crate must define panicking for libcore to use. The current |
| 4 | +//! means that the functions inside of core are allowed to panic, but to be |
| 5 | +//! useful an upstream crate must define panicking for core to use. The current |
6 | 6 | //! interface for panicking is:
|
7 | 7 | //!
|
8 | 8 | //! ```
|
|
13 | 13 | //! This definition allows for panicking with any general message, but it does not
|
14 | 14 | //! allow for failing with a `Box<Any>` value. (`PanicInfo` just contains a `&(dyn Any + Send)`,
|
15 | 15 | //! for which we fill in a dummy value in `PanicInfo::internal_constructor`.)
|
16 |
| -//! The reason for this is that libcore is not allowed to allocate. |
| 16 | +//! The reason for this is that core is not allowed to allocate. |
17 | 17 | //!
|
18 | 18 | //! This module contains a few other panicking functions, but these are just the
|
19 | 19 | //! necessary lang items for the compiler. All panics are funneled through this
|
@@ -94,7 +94,7 @@ pub fn panic_nounwind(msg: &'static str) -> ! {
|
94 | 94 | // Next we define a bunch of higher-level wrappers that all bottom out in the two core functions
|
95 | 95 | // above.
|
96 | 96 |
|
97 |
| -/// The underlying implementation of libcore's `panic!` macro when no formatting is used. |
| 97 | +/// The underlying implementation of core's `panic!` macro when no formatting is used. |
98 | 98 | // never inline unless panic_immediate_abort to avoid code
|
99 | 99 | // bloat at the call sites as much as possible
|
100 | 100 | #[cfg_attr(not(feature = "panic_immediate_abort"), inline(never), cold)]
|
|
0 commit comments