2014-01-24 01:40:54 -06:00
|
|
|
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
2014-02-16 23:40:26 -06:00
|
|
|
|
|
|
|
//! Standard library macros
|
|
|
|
//!
|
|
|
|
//! This modules contains a set of macros which are exported from the standard
|
|
|
|
//! library. Each macro is available for use when linking against the standard
|
|
|
|
//! library.
|
|
|
|
|
2014-06-30 19:22:40 -05:00
|
|
|
#![experimental]
|
2014-01-24 01:40:54 -06:00
|
|
|
|
2014-12-27 15:57:43 -06:00
|
|
|
/// The entry point for panic of Rust tasks.
|
|
|
|
///
|
|
|
|
/// This macro is used to inject panic into a Rust task, causing the task to
|
|
|
|
/// unwind and panic entirely. Each task's panic can be reaped as the
|
|
|
|
/// `Box<Any>` type, and the single-argument form of the `panic!` macro will be
|
|
|
|
/// the value which is transmitted.
|
|
|
|
///
|
|
|
|
/// The multi-argument form of this macro panics with a string and has the
|
|
|
|
/// `format!` syntax for building a string.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```should_fail
|
|
|
|
/// # #![allow(unreachable_code)]
|
|
|
|
/// panic!();
|
|
|
|
/// panic!("this is a terrible mistake!");
|
2015-01-05 21:08:37 -06:00
|
|
|
/// panic!(4i); // panic with the value of 4 to be collected elsewhere
|
2014-12-27 15:57:43 -06:00
|
|
|
/// panic!("this is a {} {message}", "fancy", message = "message");
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[stable]
|
2014-12-27 15:57:43 -06:00
|
|
|
macro_rules! panic {
|
|
|
|
() => ({
|
|
|
|
panic!("explicit panic")
|
|
|
|
});
|
|
|
|
($msg:expr) => ({
|
2015-01-06 13:07:09 -06:00
|
|
|
$crate::rt::begin_unwind($msg, {
|
|
|
|
// static requires less code at runtime, more constant data
|
|
|
|
static _FILE_LINE: (&'static str, uint) = (file!(), line!());
|
|
|
|
&_FILE_LINE
|
|
|
|
})
|
2014-12-27 15:57:43 -06:00
|
|
|
});
|
2015-01-06 13:07:09 -06:00
|
|
|
($fmt:expr, $($arg:tt)+) => ({
|
|
|
|
$crate::rt::begin_unwind_fmt(format_args!($fmt, $($arg)+), {
|
|
|
|
// The leading _'s are to avoid dead code warnings if this is
|
|
|
|
// used inside a dead function. Just `#[allow(dead_code)]` is
|
|
|
|
// insufficient, since the user may have
|
|
|
|
// `#[forbid(dead_code)]` and which cannot be overridden.
|
|
|
|
static _FILE_LINE: (&'static str, uint) = (file!(), line!());
|
|
|
|
&_FILE_LINE
|
|
|
|
})
|
2014-12-27 15:57:43 -06:00
|
|
|
});
|
|
|
|
}
|
|
|
|
|
2014-02-16 23:40:26 -06:00
|
|
|
/// Ensure that a boolean expression is `true` at runtime.
|
|
|
|
///
|
2014-10-09 14:17:22 -05:00
|
|
|
/// This will invoke the `panic!` macro if the provided expression cannot be
|
2014-02-16 23:40:26 -06:00
|
|
|
/// evaluated to `true` at runtime.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2014-10-09 14:17:22 -05:00
|
|
|
/// // the panic message for these assertions is the stringified value of the
|
2014-02-16 23:40:26 -06:00
|
|
|
/// // expression given.
|
|
|
|
/// assert!(true);
|
|
|
|
/// # fn some_computation() -> bool { true }
|
|
|
|
/// assert!(some_computation());
|
|
|
|
///
|
|
|
|
/// // assert with a custom message
|
|
|
|
/// # let x = true;
|
|
|
|
/// assert!(x, "x wasn't true!");
|
2015-01-05 21:08:37 -06:00
|
|
|
/// # let a = 3i; let b = 27i;
|
2014-02-16 23:40:26 -06:00
|
|
|
/// assert!(a + b == 30, "a = {}, b = {}", a, b);
|
|
|
|
/// ```
|
2014-01-24 01:40:54 -06:00
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[stable]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! assert {
|
2014-02-07 11:42:11 -06:00
|
|
|
($cond:expr) => (
|
2014-01-24 01:40:54 -06:00
|
|
|
if !$cond {
|
2014-10-09 14:17:22 -05:00
|
|
|
panic!(concat!("assertion failed: ", stringify!($cond)))
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
2014-02-07 11:42:11 -06:00
|
|
|
);
|
2015-01-06 13:07:09 -06:00
|
|
|
($cond:expr, $($arg:tt)+) => (
|
2014-01-24 01:40:54 -06:00
|
|
|
if !$cond {
|
2015-01-06 13:07:09 -06:00
|
|
|
panic!($($arg)+)
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
2014-02-07 11:42:11 -06:00
|
|
|
);
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-01-24 01:40:54 -06:00
|
|
|
|
2014-02-16 23:40:26 -06:00
|
|
|
/// Asserts that two expressions are equal to each other, testing equality in
|
|
|
|
/// both directions.
|
|
|
|
///
|
2014-10-09 14:17:22 -05:00
|
|
|
/// On panic, this macro will print the values of the expressions.
|
2014-02-16 23:40:26 -06:00
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2015-01-05 21:08:37 -06:00
|
|
|
/// let a = 3i;
|
|
|
|
/// let b = 1i + 2i;
|
2014-02-16 23:40:26 -06:00
|
|
|
/// assert_eq!(a, b);
|
|
|
|
/// ```
|
2014-01-24 01:40:54 -06:00
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[stable]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! assert_eq {
|
2014-12-08 17:12:03 -06:00
|
|
|
($left:expr , $right:expr) => ({
|
|
|
|
match (&($left), &($right)) {
|
|
|
|
(left_val, right_val) => {
|
2014-04-07 07:32:49 -05:00
|
|
|
// check both directions of equality....
|
2014-12-08 17:12:03 -06:00
|
|
|
if !((*left_val == *right_val) &&
|
|
|
|
(*right_val == *left_val)) {
|
2014-10-09 14:17:22 -05:00
|
|
|
panic!("assertion failed: `(left == right) && (right == left)` \
|
2014-12-20 02:09:35 -06:00
|
|
|
(left: `{:?}`, right: `{:?}`)", *left_val, *right_val)
|
2014-04-07 07:32:49 -05:00
|
|
|
}
|
|
|
|
}
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
2014-02-07 11:42:11 -06:00
|
|
|
})
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-01-24 01:40:54 -06:00
|
|
|
|
2014-04-26 20:25:20 -05:00
|
|
|
/// Ensure that a boolean expression is `true` at runtime.
|
|
|
|
///
|
2014-10-09 14:17:22 -05:00
|
|
|
/// This will invoke the `panic!` macro if the provided expression cannot be
|
2014-04-26 20:25:20 -05:00
|
|
|
/// evaluated to `true` at runtime.
|
|
|
|
///
|
|
|
|
/// Unlike `assert!`, `debug_assert!` statements can be disabled by passing
|
|
|
|
/// `--cfg ndebug` to the compiler. This makes `debug_assert!` useful for
|
|
|
|
/// checks that are too expensive to be present in a release build but may be
|
|
|
|
/// helpful during development.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2014-10-09 14:17:22 -05:00
|
|
|
/// // the panic message for these assertions is the stringified value of the
|
2014-04-26 20:25:20 -05:00
|
|
|
/// // expression given.
|
|
|
|
/// debug_assert!(true);
|
|
|
|
/// # fn some_expensive_computation() -> bool { true }
|
|
|
|
/// debug_assert!(some_expensive_computation());
|
|
|
|
///
|
|
|
|
/// // assert with a custom message
|
|
|
|
/// # let x = true;
|
|
|
|
/// debug_assert!(x, "x wasn't true!");
|
2015-01-05 21:08:37 -06:00
|
|
|
/// # let a = 3i; let b = 27i;
|
2014-04-26 20:25:20 -05:00
|
|
|
/// debug_assert!(a + b == 30, "a = {}, b = {}", a, b);
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[stable]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! debug_assert {
|
2014-04-26 20:25:20 -05:00
|
|
|
($($arg:tt)*) => (if cfg!(not(ndebug)) { assert!($($arg)*); })
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-04-26 20:25:20 -05:00
|
|
|
|
|
|
|
/// Asserts that two expressions are equal to each other, testing equality in
|
|
|
|
/// both directions.
|
|
|
|
///
|
2014-10-09 14:17:22 -05:00
|
|
|
/// On panic, this macro will print the values of the expressions.
|
2014-04-26 20:25:20 -05:00
|
|
|
///
|
|
|
|
/// Unlike `assert_eq!`, `debug_assert_eq!` statements can be disabled by
|
|
|
|
/// passing `--cfg ndebug` to the compiler. This makes `debug_assert_eq!`
|
|
|
|
/// useful for checks that are too expensive to be present in a release build
|
|
|
|
/// but may be helpful during development.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2015-01-05 21:08:37 -06:00
|
|
|
/// let a = 3i;
|
|
|
|
/// let b = 1i + 2i;
|
2014-04-26 20:25:20 -05:00
|
|
|
/// debug_assert_eq!(a, b);
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! debug_assert_eq {
|
2014-04-26 20:25:20 -05:00
|
|
|
($($arg:tt)*) => (if cfg!(not(ndebug)) { assert_eq!($($arg)*); })
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-04-26 20:25:20 -05:00
|
|
|
|
2014-11-25 11:26:14 -06:00
|
|
|
/// A utility macro for indicating unreachable code.
|
2014-01-24 01:40:54 -06:00
|
|
|
///
|
2014-11-25 11:26:14 -06:00
|
|
|
/// This is useful any time that the compiler can't determine that some code is unreachable. For
|
|
|
|
/// example:
|
|
|
|
///
|
|
|
|
/// * Match arms with guard conditions.
|
|
|
|
/// * Loops that dynamically terminate.
|
|
|
|
/// * Iterators that dynamically terminate.
|
|
|
|
///
|
|
|
|
/// # Panics
|
|
|
|
///
|
|
|
|
/// This will always panic.
|
|
|
|
///
|
|
|
|
/// # Examples
|
|
|
|
///
|
|
|
|
/// Match arms:
|
2014-01-24 01:40:54 -06:00
|
|
|
///
|
2014-11-25 11:26:14 -06:00
|
|
|
/// ```rust
|
|
|
|
/// fn foo(x: Option<int>) {
|
2014-11-26 12:21:45 -06:00
|
|
|
/// match x {
|
|
|
|
/// Some(n) if n >= 0 => println!("Some(Non-negative)"),
|
|
|
|
/// Some(n) if n < 0 => println!("Some(Negative)"),
|
|
|
|
/// Some(_) => unreachable!(), // compile error if commented out
|
|
|
|
/// None => println!("None")
|
|
|
|
/// }
|
2014-11-25 11:26:14 -06:00
|
|
|
/// }
|
|
|
|
/// ```
|
|
|
|
///
|
|
|
|
/// Iterators:
|
|
|
|
///
|
|
|
|
/// ```rust
|
2014-11-27 08:25:29 -06:00
|
|
|
/// fn divide_by_three(x: u32) -> u32 { // one of the poorest implementations of x/3
|
|
|
|
/// for i in std::iter::count(0_u32, 1) {
|
|
|
|
/// if 3*i < i { panic!("u32 overflow"); }
|
|
|
|
/// if x < 3*i { return i-1; }
|
2014-01-24 01:40:54 -06:00
|
|
|
/// }
|
|
|
|
/// unreachable!();
|
|
|
|
/// }
|
2014-09-16 06:27:34 -05:00
|
|
|
/// ```
|
2014-01-24 01:40:54 -06:00
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[unstable = "relationship with panic is unclear"]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! unreachable {
|
2014-11-10 21:33:20 -06:00
|
|
|
() => ({
|
|
|
|
panic!("internal error: entered unreachable code")
|
|
|
|
});
|
|
|
|
($msg:expr) => ({
|
|
|
|
unreachable!("{}", $msg)
|
|
|
|
});
|
|
|
|
($fmt:expr, $($arg:tt)*) => ({
|
|
|
|
panic!(concat!("internal error: entered unreachable code: ", $fmt), $($arg)*)
|
|
|
|
});
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-01-24 01:40:54 -06:00
|
|
|
|
2014-10-09 14:17:22 -05:00
|
|
|
/// A standardised placeholder for marking unfinished code. It panics with the
|
2014-02-07 04:18:17 -06:00
|
|
|
/// message `"not yet implemented"` when executed.
|
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[unstable = "relationship with panic is unclear"]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! unimplemented {
|
2014-10-09 14:17:22 -05:00
|
|
|
() => (panic!("not yet implemented"))
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-02-07 04:18:17 -06:00
|
|
|
|
2014-12-27 15:57:43 -06:00
|
|
|
/// Use the syntax described in `std::fmt` to create a value of type `String`.
|
|
|
|
/// See `std::fmt` for more information.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// format!("test");
|
|
|
|
/// format!("hello {}", "world!");
|
2015-01-05 21:08:37 -06:00
|
|
|
/// format!("x = {}, y = {y}", 10i, y = 30i);
|
2014-12-27 15:57:43 -06:00
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
|
|
|
#[stable]
|
|
|
|
macro_rules! format {
|
2015-01-06 13:07:09 -06:00
|
|
|
($($arg:tt)*) => ($crate::fmt::format(format_args!($($arg)*)))
|
2014-12-27 15:57:43 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/// Equivalent to the `println!` macro except that a newline is not printed at
|
|
|
|
/// the end of the message.
|
|
|
|
#[macro_export]
|
|
|
|
#[stable]
|
|
|
|
macro_rules! print {
|
2015-01-06 13:07:09 -06:00
|
|
|
($($arg:tt)*) => ($crate::io::stdio::print_args(format_args!($($arg)*)))
|
2014-12-27 15:57:43 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/// Macro for printing to a task's stdout handle.
|
|
|
|
///
|
|
|
|
/// Each task can override its stdout handle via `std::io::stdio::set_stdout`.
|
|
|
|
/// The syntax of this macro is the same as that used for `format!`. For more
|
|
|
|
/// information, see `std::fmt` and `std::io::stdio`.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// println!("hello there!");
|
|
|
|
/// println!("format {} arguments", "some");
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
|
|
|
#[stable]
|
|
|
|
macro_rules! println {
|
2015-01-06 13:07:09 -06:00
|
|
|
($($arg:tt)*) => ($crate::io::stdio::println_args(format_args!($($arg)*)))
|
2014-12-27 15:57:43 -06:00
|
|
|
}
|
|
|
|
|
2014-02-16 23:40:26 -06:00
|
|
|
/// Helper macro for unwrapping `Result` values while returning early with an
|
|
|
|
/// error if the value of the expression is `Err`. For more information, see
|
|
|
|
/// `std::io`.
|
2014-01-29 18:33:57 -06:00
|
|
|
#[macro_export]
|
2015-01-06 13:07:09 -06:00
|
|
|
#[stable]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! try {
|
2015-01-06 13:07:09 -06:00
|
|
|
($expr:expr) => (match $expr {
|
|
|
|
$crate::result::Result::Ok(val) => val,
|
|
|
|
$crate::result::Result::Err(err) => {
|
|
|
|
return $crate::result::Result::Err($crate::error::FromError::from_error(err))
|
2014-10-03 16:23:09 -05:00
|
|
|
}
|
|
|
|
})
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-02-18 23:36:51 -06:00
|
|
|
|
2014-05-27 09:20:06 -05:00
|
|
|
/// A macro to select an event from a number of receivers.
|
2014-02-23 23:30:18 -06:00
|
|
|
///
|
|
|
|
/// This macro is used to wait for the first event to occur on a number of
|
2014-05-27 09:20:06 -05:00
|
|
|
/// receivers. It places no restrictions on the types of receivers given to
|
|
|
|
/// this macro, this can be viewed as a heterogeneous select.
|
2014-02-23 23:30:18 -06:00
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2014-12-14 02:05:32 -06:00
|
|
|
/// use std::thread::Thread;
|
2014-12-23 13:53:35 -06:00
|
|
|
/// use std::sync::mpsc::channel;
|
2014-12-14 02:05:32 -06:00
|
|
|
///
|
2014-03-09 16:58:32 -05:00
|
|
|
/// let (tx1, rx1) = channel();
|
|
|
|
/// let (tx2, rx2) = channel();
|
2014-02-23 23:30:18 -06:00
|
|
|
/// # fn long_running_task() {}
|
2015-01-05 21:08:37 -06:00
|
|
|
/// # fn calculate_the_answer() -> int { 42i }
|
2014-02-23 23:30:18 -06:00
|
|
|
///
|
2015-01-05 23:59:45 -06:00
|
|
|
/// Thread::spawn(move|| { long_running_task(); tx1.send(()).unwrap(); });
|
|
|
|
/// Thread::spawn(move|| { tx2.send(calculate_the_answer()).unwrap(); });
|
2014-02-23 23:30:18 -06:00
|
|
|
///
|
|
|
|
/// select! (
|
2014-12-23 13:53:35 -06:00
|
|
|
/// _ = rx1.recv() => println!("the long running task finished first"),
|
2014-03-09 16:58:32 -05:00
|
|
|
/// answer = rx2.recv() => {
|
2014-12-23 13:53:35 -06:00
|
|
|
/// println!("the answer was: {}", answer.unwrap());
|
2014-02-23 23:30:18 -06:00
|
|
|
/// }
|
|
|
|
/// )
|
|
|
|
/// ```
|
|
|
|
///
|
2014-12-23 13:53:35 -06:00
|
|
|
/// For more information about select, see the `std::sync::mpsc::Select` structure.
|
2014-02-23 23:30:18 -06:00
|
|
|
#[macro_export]
|
|
|
|
#[experimental]
|
|
|
|
macro_rules! select {
|
|
|
|
(
|
2014-03-09 16:58:32 -05:00
|
|
|
$($name:pat = $rx:ident.$meth:ident() => $code:expr),+
|
2014-02-23 23:30:18 -06:00
|
|
|
) => ({
|
2014-09-15 21:29:47 -05:00
|
|
|
use $crate::sync::mpsc::Select;
|
2014-02-23 23:30:18 -06:00
|
|
|
let sel = Select::new();
|
2014-03-09 16:58:32 -05:00
|
|
|
$( let mut $rx = sel.handle(&$rx); )+
|
2014-02-23 23:30:18 -06:00
|
|
|
unsafe {
|
2014-03-09 16:58:32 -05:00
|
|
|
$( $rx.add(); )+
|
2014-02-23 23:30:18 -06:00
|
|
|
}
|
|
|
|
let ret = sel.wait();
|
2014-03-09 16:58:32 -05:00
|
|
|
$( if ret == $rx.id() { let $name = $rx.$meth(); $code } else )+
|
2014-02-23 23:30:18 -06:00
|
|
|
{ unreachable!() }
|
|
|
|
})
|
|
|
|
}
|
log: Introduce liblog, the old std::logging
This commit moves all logging out of the standard library into an external
crate. This crate is the new crate which is responsible for all logging macros
and logging implementation. A few reasons for this change are:
* The crate map has always been a bit of a code smell among rust programs. It
has difficulty being loaded on almost all platforms, and it's used almost
exclusively for logging and only logging. Removing the crate map is one of the
end goals of this movement.
* The compiler has a fair bit of special support for logging. It has the
__log_level() expression as well as generating a global word per module
specifying the log level. This is unfairly favoring the built-in logging
system, and is much better done purely in libraries instead of the compiler
itself.
* Initialization of logging is much easier to do if there is no reliance on a
magical crate map being available to set module log levels.
* If the logging library can be written outside of the standard library, there's
no reason that it shouldn't be. It's likely that we're not going to build the
highest quality logging library of all time, so third-party libraries should
be able to provide just as high-quality logging systems as the default one
provided in the rust distribution.
With a migration such as this, the change does not come for free. There are some
subtle changes in the behavior of liblog vs the previous logging macros:
* The core change of this migration is that there is no longer a physical
log-level per module. This concept is still emulated (it is quite useful), but
there is now only a global log level, not a local one. This global log level
is a reflection of the maximum of all log levels specified. The previously
generated logging code looked like:
if specified_level <= __module_log_level() {
println!(...)
}
The newly generated code looks like:
if specified_level <= ::log::LOG_LEVEL {
if ::log::module_enabled(module_path!()) {
println!(...)
}
}
Notably, the first layer of checking is still intended to be "super fast" in
that it's just a load of a global word and a compare. The second layer of
checking is executed to determine if the current module does indeed have
logging turned on.
This means that if any module has a debug log level turned on, all modules
with debug log levels get a little bit slower (they all do more expensive
dynamic checks to determine if they're turned on or not).
Semantically, this migration brings no change in this respect, but
runtime-wise, this will have a perf impact on some code.
* A `RUST_LOG=::help` directive will no longer print out a list of all modules
that can be logged. This is because the crate map will no longer specify the
log levels of all modules, so the list of modules is not known. Additionally,
warnings can no longer be provided if a malformed logging directive was
supplied.
The new "hello world" for logging looks like:
#[phase(syntax, link)]
extern crate log;
fn main() {
debug!("Hello, world!");
}
2014-03-09 00:11:44 -06:00
|
|
|
|
|
|
|
// When testing the standard library, we link to the liblog crate to get the
|
|
|
|
// logging macros. In doing so, the liblog crate was linked against the real
|
|
|
|
// version of libstd, and uses a different std::fmt module than the test crate
|
|
|
|
// uses. To get around this difference, we redefine the log!() macro here to be
|
|
|
|
// just a dumb version of what it should be.
|
|
|
|
#[cfg(test)]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! log {
|
log: Introduce liblog, the old std::logging
This commit moves all logging out of the standard library into an external
crate. This crate is the new crate which is responsible for all logging macros
and logging implementation. A few reasons for this change are:
* The crate map has always been a bit of a code smell among rust programs. It
has difficulty being loaded on almost all platforms, and it's used almost
exclusively for logging and only logging. Removing the crate map is one of the
end goals of this movement.
* The compiler has a fair bit of special support for logging. It has the
__log_level() expression as well as generating a global word per module
specifying the log level. This is unfairly favoring the built-in logging
system, and is much better done purely in libraries instead of the compiler
itself.
* Initialization of logging is much easier to do if there is no reliance on a
magical crate map being available to set module log levels.
* If the logging library can be written outside of the standard library, there's
no reason that it shouldn't be. It's likely that we're not going to build the
highest quality logging library of all time, so third-party libraries should
be able to provide just as high-quality logging systems as the default one
provided in the rust distribution.
With a migration such as this, the change does not come for free. There are some
subtle changes in the behavior of liblog vs the previous logging macros:
* The core change of this migration is that there is no longer a physical
log-level per module. This concept is still emulated (it is quite useful), but
there is now only a global log level, not a local one. This global log level
is a reflection of the maximum of all log levels specified. The previously
generated logging code looked like:
if specified_level <= __module_log_level() {
println!(...)
}
The newly generated code looks like:
if specified_level <= ::log::LOG_LEVEL {
if ::log::module_enabled(module_path!()) {
println!(...)
}
}
Notably, the first layer of checking is still intended to be "super fast" in
that it's just a load of a global word and a compare. The second layer of
checking is executed to determine if the current module does indeed have
logging turned on.
This means that if any module has a debug log level turned on, all modules
with debug log levels get a little bit slower (they all do more expensive
dynamic checks to determine if they're turned on or not).
Semantically, this migration brings no change in this respect, but
runtime-wise, this will have a perf impact on some code.
* A `RUST_LOG=::help` directive will no longer print out a list of all modules
that can be logged. This is because the crate map will no longer specify the
log levels of all modules, so the list of modules is not known. Additionally,
warnings can no longer be provided if a malformed logging directive was
supplied.
The new "hello world" for logging looks like:
#[phase(syntax, link)]
extern crate log;
fn main() {
debug!("Hello, world!");
}
2014-03-09 00:11:44 -06:00
|
|
|
($lvl:expr, $($args:tt)*) => (
|
|
|
|
if log_enabled!($lvl) { println!($($args)*) }
|
|
|
|
)
|
2014-11-14 11:18:10 -06:00
|
|
|
}
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Built-in macros to the compiler itself.
|
|
|
|
///
|
|
|
|
/// These macros do not have any corresponding definition with a `macro_rules!`
|
|
|
|
/// macro, but are documented here. Their implementations can be found hardcoded
|
|
|
|
/// into libsyntax itself.
|
|
|
|
#[cfg(dox)]
|
|
|
|
pub mod builtin {
|
|
|
|
/// The core macro for formatted string creation & output.
|
|
|
|
///
|
2014-12-27 15:57:43 -06:00
|
|
|
/// This macro produces a value of type `fmt::Arguments`. This value can be
|
|
|
|
/// passed to the functions in `std::fmt` for performing useful functions.
|
|
|
|
/// All other formatting macros (`format!`, `write!`, `println!`, etc) are
|
|
|
|
/// proxied through this one.
|
2014-04-01 17:04:42 -05:00
|
|
|
///
|
|
|
|
/// For more information, see the documentation in `std::fmt`.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// use std::fmt;
|
|
|
|
///
|
2014-12-27 15:57:43 -06:00
|
|
|
/// let s = fmt::format(format_args!("hello {}", "world"));
|
2014-04-01 17:04:42 -05:00
|
|
|
/// assert_eq!(s, format!("hello {}", "world"));
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2015-01-06 18:16:35 -06:00
|
|
|
macro_rules! format_args { ($fmt:expr, $($args:tt)*) => ({
|
2014-04-01 17:04:42 -05:00
|
|
|
/* compiler built-in */
|
2014-11-14 11:18:10 -06:00
|
|
|
}) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Inspect an environment variable at compile time.
|
|
|
|
///
|
|
|
|
/// This macro will expand to the value of the named environment variable at
|
|
|
|
/// compile time, yielding an expression of type `&'static str`.
|
|
|
|
///
|
|
|
|
/// If the environment variable is not defined, then a compilation error
|
|
|
|
/// will be emitted. To not emit a compile error, use the `option_env!`
|
|
|
|
/// macro instead.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust
|
2014-09-16 15:51:01 -05:00
|
|
|
/// let path: &'static str = env!("PATH");
|
|
|
|
/// println!("the $PATH variable at the time of compiling was: {}", path);
|
2014-04-01 17:04:42 -05:00
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! env { ($name:expr) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Optionally inspect an environment variable at compile time.
|
|
|
|
///
|
|
|
|
/// If the named environment variable is present at compile time, this will
|
|
|
|
/// expand into an expression of type `Option<&'static str>` whose value is
|
|
|
|
/// `Some` of the value of the environment variable. If the environment
|
|
|
|
/// variable is not present, then this will expand to `None`.
|
|
|
|
///
|
|
|
|
/// A compile time error is never emitted when using this macro regardless
|
|
|
|
/// of whether the environment variable is present or not.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// let key: Option<&'static str> = option_env!("SECRET_KEY");
|
2015-01-06 18:16:35 -06:00
|
|
|
/// println!("the secret key might be: {:?}", key);
|
2014-04-01 17:04:42 -05:00
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! option_env { ($name:expr) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Concatenate identifiers into one identifier.
|
|
|
|
///
|
|
|
|
/// This macro takes any number of comma-separated identifiers, and
|
|
|
|
/// concatenates them all into one, yielding an expression which is a new
|
|
|
|
/// identifier. Note that hygiene makes it such that this macro cannot
|
|
|
|
/// capture local variables, and macros are only allowed in item,
|
|
|
|
/// statement or expression position, meaning this macro may be difficult to
|
|
|
|
/// use in some situations.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2014-06-06 11:22:19 -05:00
|
|
|
/// #![feature(concat_idents)]
|
|
|
|
///
|
|
|
|
/// # fn main() {
|
2014-04-01 17:04:42 -05:00
|
|
|
/// fn foobar() -> int { 23 }
|
|
|
|
///
|
|
|
|
/// let f = concat_idents!(foo, bar);
|
|
|
|
/// println!("{}", f());
|
2014-06-06 11:22:19 -05:00
|
|
|
/// # }
|
2014-04-01 17:04:42 -05:00
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! concat_idents {
|
|
|
|
($($e:ident),*) => ({ /* compiler built-in */ })
|
|
|
|
}
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Concatenates literals into a static string slice.
|
|
|
|
///
|
|
|
|
/// This macro takes any number of comma-separated literals, yielding an
|
|
|
|
/// expression of type `&'static str` which represents all of the literals
|
|
|
|
/// concatenated left-to-right.
|
|
|
|
///
|
|
|
|
/// Integer and floating point literals are stringified in order to be
|
|
|
|
/// concatenated.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2015-01-05 21:08:37 -06:00
|
|
|
/// let s = concat!("test", 10i, 'b', true);
|
2014-04-01 17:04:42 -05:00
|
|
|
/// assert_eq!(s, "test10btrue");
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! concat { ($($e:expr),*) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// A macro which expands to the line number on which it was invoked.
|
|
|
|
///
|
|
|
|
/// The expanded expression has type `uint`, and the returned line is not
|
|
|
|
/// the invocation of the `line!()` macro itself, but rather the first macro
|
|
|
|
/// invocation leading up to the invocation of the `line!()` macro.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// let current_line = line!();
|
|
|
|
/// println!("defined on line: {}", current_line);
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! line { () => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// A macro which expands to the column number on which it was invoked.
|
|
|
|
///
|
|
|
|
/// The expanded expression has type `uint`, and the returned column is not
|
2014-11-18 06:03:58 -06:00
|
|
|
/// the invocation of the `column!()` macro itself, but rather the first macro
|
|
|
|
/// invocation leading up to the invocation of the `column!()` macro.
|
2014-04-01 17:04:42 -05:00
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
2014-11-18 06:03:58 -06:00
|
|
|
/// let current_col = column!();
|
2014-04-01 17:04:42 -05:00
|
|
|
/// println!("defined on column: {}", current_col);
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! column { () => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// A macro which expands to the file name from which it was invoked.
|
|
|
|
///
|
|
|
|
/// The expanded expression has type `&'static str`, and the returned file
|
|
|
|
/// is not the invocation of the `file!()` macro itself, but rather the
|
|
|
|
/// first macro invocation leading up to the invocation of the `file!()`
|
|
|
|
/// macro.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// let this_file = file!();
|
|
|
|
/// println!("defined in file: {}", this_file);
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! file { () => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// A macro which stringifies its argument.
|
|
|
|
///
|
|
|
|
/// This macro will yield an expression of type `&'static str` which is the
|
|
|
|
/// stringification of all the tokens passed to the macro. No restrictions
|
|
|
|
/// are placed on the syntax of the macro invocation itself.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```
|
|
|
|
/// let one_plus_one = stringify!(1 + 1);
|
|
|
|
/// assert_eq!(one_plus_one, "1 + 1");
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! stringify { ($t:tt) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Includes a utf8-encoded file as a string.
|
|
|
|
///
|
|
|
|
/// This macro will yield an expression of type `&'static str` which is the
|
|
|
|
/// contents of the filename specified. The file is located relative to the
|
|
|
|
/// current file (similarly to how modules are found),
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust,ignore
|
|
|
|
/// let secret_key = include_str!("secret-key.ascii");
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! include_str { ($file:expr) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Includes a file as a byte slice.
|
|
|
|
///
|
|
|
|
/// This macro will yield an expression of type `&'static [u8]` which is
|
|
|
|
/// the contents of the filename specified. The file is located relative to
|
|
|
|
/// the current file (similarly to how modules are found),
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust,ignore
|
2014-12-21 15:57:09 -06:00
|
|
|
/// let secret_key = include_bytes!("secret-key.bin");
|
2014-04-01 17:04:42 -05:00
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-12-21 15:57:09 -06:00
|
|
|
macro_rules! include_bytes { ($file:expr) => ({ /* compiler built-in */ }) }
|
|
|
|
|
2014-04-01 17:04:42 -05:00
|
|
|
/// Expands to a string that represents the current module path.
|
|
|
|
///
|
|
|
|
/// The current module path can be thought of as the hierarchy of modules
|
|
|
|
/// leading back up to the crate root. The first component of the path
|
|
|
|
/// returned is the name of the crate currently being compiled.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// mod test {
|
|
|
|
/// pub fn foo() {
|
|
|
|
/// assert!(module_path!().ends_with("test"));
|
|
|
|
/// }
|
|
|
|
/// }
|
|
|
|
///
|
|
|
|
/// test::foo();
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! module_path { () => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
|
|
|
|
/// Boolean evaluation of configuration flags.
|
|
|
|
///
|
|
|
|
/// In addition to the `#[cfg]` attribute, this macro is provided to allow
|
|
|
|
/// boolean expression evaluation of configuration flags. This frequently
|
|
|
|
/// leads to less duplicated code.
|
|
|
|
///
|
|
|
|
/// The syntax given to this macro is the same syntax as the `cfg`
|
|
|
|
/// attribute.
|
|
|
|
///
|
|
|
|
/// # Example
|
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// let my_directory = if cfg!(windows) {
|
|
|
|
/// "windows-specific-directory"
|
|
|
|
/// } else {
|
|
|
|
/// "unix-directory"
|
|
|
|
/// };
|
|
|
|
/// ```
|
|
|
|
#[macro_export]
|
2014-11-14 11:18:10 -06:00
|
|
|
macro_rules! cfg { ($cfg:tt) => ({ /* compiler built-in */ }) }
|
2014-04-01 17:04:42 -05:00
|
|
|
}
|