Philipp Schuster

Reopened as the criteria of 25+ stars is now met

@LongHairedHacker how about ``` if target.contains("linux") { println!("cargo:rustc-link-lib=asound"); println!("cargo:rustc-link-lib=pulse"); println!("cargo:rustc-link-lib=jack"); } ``` Works for me. I ran into the same issue on my Raspberry Pi

I'm still unsure but I think with this approach, we might have a less invasive approach while still having idiomatic Rust - What do you think, @YtvwlD ?

Obsolete as new API was too breaking. This needs a new approach. However, I think it can be nicely integrated in the new `multiboot2-common` lib

Thanks @an-owl - that's awesome!

~I'm 99.9% sure that the current crate is memory-safe. Unit tests, integration tests, at least a partial miri coverage. However, having miri on your side is a benefit, of course.~...

I created a minimal reproducer for the miri issue. `cast_tag` causes the problem. I also tried to solve it by giving all tags a `'a` lifetime. Didn't work ```rust use...

This patch solves the miri issues: ```diff 0a1 > use ptr_meta::Pointee; 3d3 < use ptr_meta::Pointee; 51,53c51,60 < fn cast_tag(tag: &'a BaseTag) -> &'a T { < let ptr = core::ptr::addr_of!(*tag);...

A [lively discussion on Reddit](https://www.reddit.com/r/rust/comments/1eqgmzk/help_understanding_mitigating_this_ub_detected_by/) (thanks everyone!) pointed out that my assumption was wrong. My assumption was that one can access memory outside the scope of a function if the...

Thanks @YtvwlD 🥳