Use backticks for the unsafe keyword in error messages

This commit is contained in:
Alex Crichton 2013-04-23 02:06:47 -04:00
parent 3867470feb
commit 8884c6abdb
2 changed files with 6 additions and 6 deletions

View File

@ -262,7 +262,7 @@ pub fn get_lint_dict() -> LintDict {
(~"unused_unsafe",
LintSpec {
lint: unused_unsafe,
desc: "unnecessary use of an \"unsafe\" block",
desc: "unnecessary use of an `unsafe` block",
default: warn
}),
@ -949,7 +949,7 @@ fn check_item_unused_unsafe(cx: ty::ctxt, it: @ast::item) {
if !cx.used_unsafe.contains(&blk.node.id) {
cx.sess.span_lint(unused_unsafe, blk.node.id, it.id,
blk.span,
~"unnecessary \"unsafe\" block");
~"unnecessary `unsafe` block");
}
}
_ => ()

View File

@ -16,10 +16,10 @@ use core::libc;
fn callback<T>(_f: &fn() -> T) -> T { fail!() }
fn bad1() { unsafe {} } //~ ERROR: unnecessary "unsafe" block
fn bad2() { unsafe { bad1() } } //~ ERROR: unnecessary "unsafe" block
unsafe fn bad4() { unsafe {} } //~ ERROR: unnecessary "unsafe" block
fn bad5() { unsafe { do callback {} } } //~ ERROR: unnecessary "unsafe" block
fn bad1() { unsafe {} } //~ ERROR: unnecessary `unsafe` block
fn bad2() { unsafe { bad1() } } //~ ERROR: unnecessary `unsafe` block
unsafe fn bad4() { unsafe {} } //~ ERROR: unnecessary `unsafe` block
fn bad5() { unsafe { do callback {} } } //~ ERROR: unnecessary `unsafe` block
unsafe fn good0() { libc::exit(1) }
fn good1() { unsafe { libc::exit(1) } }