rust/tests/ui/issues/issue-7246.rs

#![deny(unreachable_code)]
#![allow(dead_code)]

use std::ptr;
pub unsafe fn g() {
    return;
    if *ptr::null() {}; //~ ERROR unreachable
    //~| WARNING dereferencing a null pointer
}

pub fn main() {}
Convert most code to new inner attribute syntax. Closes #2569 2014-03-21 18:05:05 -07:00			`#![deny(unreachable_code)]`
			`#![allow(dead_code)]`
Add dead-code warning pass 2013-12-08 02:55:27 -05:00
testsuite: Two tests for fixed bugs Closes #7246 Closes #7573 2013-09-29 14:46:23 -07:00			`use std::ptr;`
			`pub unsafe fn g() {`
Added tests to make tidy 2014-02-05 16:33:10 -06:00			`return;`
testsuite: Two tests for fixed bugs Closes #7246 Closes #7573 2013-09-29 14:46:23 -07:00			`if *ptr::null() {}; //~ ERROR unreachable`
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors. 2021-07-20 23:23:22 -04:00			`//~\| WARNING dereferencing a null pointer`
testsuite: Two tests for fixed bugs Closes #7246 Closes #7573 2013-09-29 14:46:23 -07:00			`}`

			`pub fn main() {}`