Lines Matching refs:set_logger
182 //! Loggers are installed by calling the [`set_logger`] function. The maximum
190 //! provide a function that wraps a call to [`set_logger`] and
207 //! log::set_logger(&LOGGER)
217 //! `set_logger` requires you to provide a `&'static Log`, which can be hard to
220 //! identical to `set_logger` except that it takes a `Box<Log>` rather than a
295 //! [`set_logger`]: fn.set_logger.html
403 // uninitialized, the logger's initializing (set_logger's been called but
1396 /// This is a simple convenience wrapper over `set_logger`, which takes a
1398 /// [`set_logger`] for more details.
1406 /// [`set_logger`]: fn.set_logger.html
1415 /// events that occur before the call to `set_logger` completes will be ignored.
1455 /// log::set_logger(&MY_LOGGER).unwrap();
1466 pub fn set_logger(logger: &'static dyn Log) -> Result<(), SetLoggerError> {
1503 /// A thread-unsafe version of [`set_logger`].
1506 /// support for atomics that is needed by [`set_logger`].
1508 /// In almost all cases, [`set_logger`] should be preferred.
1521 /// [`set_logger`]: fn.set_logger.html
1537 /// The type returned by [`set_logger`] if [`set_logger`] has already been called.
1539 /// [`set_logger`]: fn.set_logger.html