Nekrolm

// https://godbolt.org/z/hfcnTfaz8
#include <cstdint>
#include <array>
#include <cstddef>
#include <ranges>
#include <algorithm>
#include <utility>
#include <format>
#include <string_view>
#include <print>

Nekrolm

#include <stdlib.h>
#include <cstdint>

#include <string>
#include <vector>
#include <map>
#include <iostream> 
#include <functional>
#include <utility>
#include <memory>

Nekrolm

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb cccccccccccccccccccccccccccccccccccccccccccccccccccc ddddddddddddddd eeeeeeeeeeeeeeeee ffffffffffffff ggggggggggg hhhhhhhhhhhhhhhhhhhhhhhhhhhhh iiiiiiiiiiiiiiiiiiiiiiiiiiiii jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk llllllllllllllllllllllllllllllllllllllllllllll mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn ooooooooooooooooooooooooooooooooo pppppppppppppppppppppppppppppppppppppppppp qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq rrrrrrrrrrrrrrrrrrrrrrrrrrrrr ssssssssssssssssssssssssssssss tttttttttttttttttttttttttt uuuuuuuuuuuuuuuuuuuuuuuuu vvvvvvvvvvvvvvvvvvvvvvvvvvvvv wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz QWERTYUIOPASDFGHJKLZXCVBNMqwertyuiopasdfghjklzxcvbnm 1234567890 QWERTYUIOPASDFGHJKLZXCVBNMqwertyuiopasdfghjklzxcvbnm123456

Nekrolm

Why unsafe is unsafe

Once I had seen this function. It was a nice function, but there is a problem

pub fn encode_logs(logs: impl IntoIterator<Item = impl AsRef<str>>) -> String {
    logs.into_iter().map(|line|
        line.as_ref()
            .replace("\\", "\\\\")
            .replace("\n", "\\n")

Nekrolm

Mock testing in Rust projects

Rust usually gives you a pleasant experience: if it compiles — it works. But strong type checking doesn’t eliminate necessity of testing. Especially if your code deals with some external dependencies:

• Have your checked the behaviour of your code on all error paths? May there be typo, incorrect condition, that passes type checks but contradicts with your intentions?
• What if dependency returns success on the first call, but error for the second?
• What if there’s sudden network issue?

To cover such cases there is a common approach — substitute, or “mock”, your dependencies by special, configurable test objects with same interface. And here our story begins.

Nekrolm

#include <concepts>
#include <functional>

template <class... Args>
constexpr inline auto make_safe = [](std::invocable<Args...> auto&& caller) {
    return [f = std::forward<decltype(caller)>(caller)](std::same_as<Args> auto&&... args) -> decltype(auto) {
        return std::invoke(f, std::forward<Args>(args)...);
    };
};

Nekrolm

use anyhow; // 1.0.100
use anyhow::Context;
use anyhow::Result;

use std::fmt::Write;
use std::marker::PhantomData;
use std::mem::ManuallyDrop;
use std::ops::{Deref, DerefMut};
use std::process::abort;

Nekrolm

use std::{env::set_current_dir, f32::consts::PI, ops::{Index, IndexMut}, time::Duration};



struct Screen<'a> {
    grid: &'a mut [ u8 ],
    width: usize,
    height: usize,
}

Nekrolm

use bumpalo::Bump;
use criterion::{criterion_group, criterion_main, Criterion};
use std::hint::black_box;

const N: usize = 10000;
const NUM_IMPLS: usize = 5;

pub trait Handler {
    fn handle(&mut self) -> u64;
}