Skip to content
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.

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

Panic during linting involving complicated match statements #1782

Closed
Ameobea opened this issue May 26, 2017 · 1 comment
Closed

Panic during linting involving complicated match statements #1782

Ameobea opened this issue May 26, 2017 · 1 comment
Labels
I-ICE Issue: Clippy panicked, giving an Internal Compilation Error (ICE) ❄️

Comments

@Ameobea
Copy link

Ameobea commented May 26, 2017

I've encountered an error when linting my project resulting in a panic while compiling.

  • Compiler Version: rustc 1.19.0-nightly (5f39668 2017-05-25)
  • Failing Code:
match Some(()) {
    Some(_) => unsafe { ptr::write(ptr::null_mut() as *mut u32, mem::transmute::<[u8; 4], _>([0, 0, 0, 255])) },
    None => unsafe { ptr::write(ptr::null_mut() as *mut u32, mem::transmute::<[u8; 4], _>([13, 246, 24, 255])) },
}

I've created a PR that includes a new test that causes a panic. I was unable to determine the cause of the panic myself or go about fixing it, however.

@Ameobea Ameobea changed the title Panic when Panic during linting involving complicated match statements May 26, 2017
@oli-obk
Copy link
Contributor

oli-obk commented May 26, 2017

It's the copy paste Lint's fault. We probably messed up something around body tables again

@phansch phansch added the I-ICE Issue: Clippy panicked, giving an Internal Compilation Error (ICE) ❄️ label May 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-ICE Issue: Clippy panicked, giving an Internal Compilation Error (ICE) ❄️
Projects
None yet
Development

No branches or pull requests

3 participants