RandyMcMillan

use std::time::{SystemTime, UNIX_EPOCH};

const EPSILON_TWEAK: f64 = f64::EPSILON * /*adjust for granularity*/ 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002;

#[derive(Debug, Clone, Copy, PartialEq)]
pub struct BlochVector {
    pub x: f64,
    pub y: f64,
    pub z: f64,
}

RandyMcMillan

use once_cell::sync::OnceCell;

// global_rt
pub fn global_rt() -> &'static tokio::runtime::Runtime {
    static RT: OnceCell<tokio::runtime::Runtime> = OnceCell::new();
    RT.get_or_init(|| tokio::runtime::Runtime::new().unwrap())
}

#[cfg(test)]
mod tests {

RandyMcMillan

use std::env;
//use std::env::consts::OS;
use std::fs;
use std::path::Path;
use std::process::{Command, Stdio};
use std::str;

fn nvm_has(command: &str) -> bool {
    Command::new("type")
        .arg(command)

RandyMcMillan

use std::str;
fn main() {
    let self_bytes: &[u8] = include_bytes!("main.rs");
    match str::from_utf8(self_bytes) {
        Ok(s) => println!("{}", s),
        Err(e) => println!("Error: {}", e),
    }
}

RandyMcMillan

//

RandyMcMillan

use std::env;

fn env_vars() {
    // Iterate over all environment variables.
    for (key, value) in env::vars() {
        println!("{}: {}", key, value);
    }

    // You can also filter the environment variables.
    println!("\nFiltered environment variables:");

RandyMcMillan

use std::env;

fn env_vars() {
    // Iterate over all environment variables.
    for (key, value) in env::vars() {
        println!("{}: {}", key, value);
    }

    // You can also filter the environment variables.
    println!("\nFiltered environment variables:");

RandyMcMillan

fn main() {
    let max_usize = std::usize::MAX;

    println!("std::usize::MAX/2: {}", std::usize::MAX / 2);
    if !is_debug() {
        let overflow_release = max_usize.wrapping_add(1);
        println!("Overflow: {}", overflow_release); // Output in release: 0
    } else {
        #[warn(arithmetic_overflow)]
        #[cfg(debug_assertions)]

RandyMcMillan

use image::{ImageBuffer, Rgb};
use sha2::{Digest, Sha256};

const COLORS: [&str; 256] = [
    "#c4b9b8", "#879f84", "#a6814c", "#ff9966", "#aa1155", "#7a81ff", "#8e473b", "#f3dfb6",
    "#dfac4c", "#4b3621", "#feff32", "#a57c5b", "#52b4ca", "#fffc79", "#879877", "#bb1133",
    "#eee9d9", "#52b4d3", "#ffff81", "#4f4554", "#c68f65", "#d2e7ca", "#0000ff", "#2ee8bb",
    "#eebb88", "#eddd59", "#7f5f00", "#eeaa11", "#35fa00", "#ffefd6", "#bb11aa", "#dab4cc",
    "#fff0db", "#987d73", "#c4fff7", "#eae0c8", "#e2c779", "#ff4d00", "#334d41", "#f83800",
    "#ddedbd", "#ffdd44", "#efd7ab", "#66eeee", "#aa3333", "#006663", "#ffb75f", "#c6bb9c",

RandyMcMillan

Caveat Emptor

I (instagibbs) was asked to draft a statement, I feel this is a fair summation of the project's direction. I might be wrong

Retiring the 80-Byte OP_RETURN Limit

Bitcoin Core’s next release will, by default, relay and mine transactions whose OP_RETURN outputs exceed 80 bytes and allow any number of these outputs. The long-standing cap, originally a gentle signal that block space should be used sparingly for non-consensus data has outlived its utility.