New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CoercePointee leaks unstable unsizing impls #135217

Open

BoxyUwU opened this issue Jan 7, 2025 · 1 comment

Assignees

Labels

A-coercions F-derive_coerce_pointee T-compiler T-types

Member

BoxyUwU commented Jan 7, 2025

#![feature(derive_coerce_pointee)]
use std::marker::PhantomData;
use std::marker::CoercePointee; 
#[derive(CoercePointee)] #[repr(transparent)]
struct MyPointer<'a, T, #[pointee] U: ?Sized> {
    ptr: &'a (T, U),
}

fn main() {
    let x = MyPointer { ptr: &(1u32, 1u32) };
    let _: MyPointer<u32, dyn Send> = x;
}

Originally posted by @lcnr in #133820 (comment)

rustbot added the needs-triage label

BoxyUwU added T-compiler A-coercions T-types F-derive_coerce_pointee and removed needs-triage labels

compiler-errors self-assigned this

Member

compiler-errors commented Jan 7, 2025

I'll take a stab at this.

ojeda mentioned this issue

Rust unstable features needed for the kernel Rust-for-Linux/linux#2

Open

89 tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment