about summary refs log tree commit diff
path: root/src/libsyntax/ext
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2013-09-11 00:36:07 -0700
committerbors <bors@rust-lang.org>2013-09-11 00:36:07 -0700
commitef6a97ddbed10ac3483c639fb27e7771fd155ebc (patch)
tree0fe567f92d372b3d756a9e935ca35a82fee514bb /src/libsyntax/ext
parentba9fa89bfb4aae53db93e9ecac31807af96356fc (diff)
parent11e9c48353a6fcbfd036e5ee58b1d4b5f572d7eb (diff)
downloadrust-ef6a97ddbed10ac3483c639fb27e7771fd155ebc.tar.gz
rust-ef6a97ddbed10ac3483c639fb27e7771fd155ebc.zip
auto merge of #9013 : alexcrichton/rust/generated-unsafe-blocks, r=sanxiyn
This way syntax extensions can generate unsafe blocks without worrying about them generating unnecessary unsafe warnings. Perhaps a special keyword could be added to be used in macros, but I don't think that's the best solution.

Currently if you use `format!` and friends in an `unsafe` block you're guaranteed to get some unused-unsafe warnings which is unfortunate. We normally do want these warnings, but I'm ok ignoring them in the case of compiler-generated unsafe blocks. I tried to do this in the least intrusive way possible, but others may have better ideas about how to do this.
Diffstat (limited to 'src/libsyntax/ext')
-rw-r--r--src/libsyntax/ext/ifmt.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libsyntax/ext/ifmt.rs b/src/libsyntax/ext/ifmt.rs
index b7722ffc297..486069db4f0 100644
--- a/src/libsyntax/ext/ifmt.rs
+++ b/src/libsyntax/ext/ifmt.rs
@@ -632,7 +632,7 @@ impl Context {
            stmts: ~[],
            expr: Some(result),
            id: ast::DUMMY_NODE_ID,
-           rules: ast::UnsafeBlock,
+           rules: ast::UnsafeBlock(ast::CompilerGenerated),
            span: self.fmtsp,
         });