substreams 0.7.6

//! Log Implementation for Substreams
//!
//! This crate implements helpful logging functions which can be used
//! in your handlers
//!

/// Logs a message at INFO level on the logger of the current substreams using interpolation of
/// runtime expressions.
///
/// The behavior is exactly like [std::format::format!] built-in Rust formatting primitive.
///
/// # Panics
///
/// `format!` panics if a formatting trait implementation returns an error.
/// This indicates an incorrect implementation
/// since `fmt::Write for String` never returns an error itself.
///
/// # Examples
///
/// ```no_run
/// use substreams::log;
///
/// log::info!("test");
/// log::info!("hello {}", "world!");
/// log::info!("x = {}, y = {y}", 10, y = 30);
/// ```
#[doc(hidden)]
#[macro_export]
macro_rules! log_info {
    // We have a special case when matching an expression directly to forward directly to `println`. This is to avoid
    // any allocation and pass directly the literal to `println` which is able to deal with. However, I'm wondering if
    // this will cause WTF moment for some cases.
    ($msg:expr) => {
        $crate::log::println($msg);
    };

    ($($arg:tt)*) => {{
        let message = std::fmt::format(format_args!($($arg)*));

        $crate::log::println(message);
    }}
}

/// Logs a message at DEBUG level on the logger of the current substreams using interpolation of
/// runtime expressions.
///
/// The behavior is exactly like [std::format::format!] built-in Rust formatting primitive.
///
/// # Panics
///
/// `format!` panics if a formatting trait implementation returns an error.
/// This indicates an incorrect implementation
/// since `fmt::Write for String` never returns an error itself.
///
/// # Examples
///
/// ```no_run
/// use substreams::log;
///
/// log::debug!("test");
/// log::debug!("hello {}", "world!");
/// log::debug!("x = {}, y = {y}", 10, y = 30);
/// ```
#[doc(hidden)]
#[macro_export]
macro_rules! log_debug {
    // We have a special case when matching an expression directly to forward directly to `println`. This is to avoid
    // any allocation and pass directly the literal to `println` which is able to deal with. However, I'm wondering if
    // this will cause WTF moment for some cases.
    ($msg:expr) => {
        $crate::log::println($msg);
    };

    ($($arg:tt)*) => {{
        let message = std::fmt::format(format_args!($($arg)*));

        $crate::log::println(message);
    }}
}

pub use log_debug as debug;
pub use log_info as info;

#[cfg_attr(not(target_arch = "wasm32"), allow(unused_variables))]
pub fn println<T: AsRef<str>>(msg: T) {
    #[cfg(target_arch = "wasm32")]
    {
        use crate::externs;
        let reference = msg.as_ref();

        unsafe {
            externs::println(reference.as_ptr(), reference.len());
        }
    }
}