#[allow(dead_code
LightNews LightNews
aesthr.com
Basically this:

I can wrap any of the specific errors coming out of various libraries into a custom error type that I can then use throughout my application so most of my code doesn't need to know about the specifics of each library while still being able to react to different error types.
use std::{error, fmt, io}; #[allow(dead_code)] #[derive(Debug)] pub enum AppError { RuntimeError, RenderError, ImageError(image::ImageError), IoError(io::Error), } impl fmt::Display for AppError { fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result { write!(f, "{:?}", self) } } impl error::Error for AppError {}
August 5, 2025 at 11:26 AM
linux.activitypub.awakari.com.ap.brid.gy
Re: [PATCH] Introduce Tyr Miguel Ojeda writes: (Summary) This type must not have interior mutability. type must not have interior mutability. +#[allow(dead_code)] Could it be `expect`? Could it be ...

Origin | Interest | Match
Awakari App
awakari.com
June 28, 2025 at 9:56 AM
piss.beauty
I submitted+merged a PR this morning that just removed some "#[allow(dead_code)]" and could only actually find like 20 lines of dead/unused to cleanup..
February 19, 2025 at 5:27 PM
metaflame.dev
right,
makes total sense, we never needed r# anyway
#[allow(dead_code)] #[derive(Debug)] struct S<'a> { i32: f64, bool: &'a str, } pub fn main() { let i8 = 128f64; let u16 = "65536"; let s = S { i32: i8, bool: u16 }; dbg!(s); }
November 17, 2024 at 3:00 PM