From e389ab18a28b71479be6f24776845cc021767193 Mon Sep 17 00:00:00 2001 From: Eduard Burtescu Date: Tue, 23 Dec 2014 15:11:24 +0200 Subject: [PATCH] rustc_back: fix fallout of merging ast::ViewItem into ast::Item. --- src/librustc_back/svh.rs | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/src/librustc_back/svh.rs b/src/librustc_back/svh.rs index b71e465b938..79d7a0ced39 100644 --- a/src/librustc_back/svh.rs +++ b/src/librustc_back/svh.rs @@ -188,7 +188,6 @@ enum SawAbiComponent<'a> { SawLifetimeDef(token::InternedString), SawMod, - SawViewItem, SawForeignItem, SawItem, SawDecl, @@ -436,19 +435,6 @@ fn visit_stmt(&mut self, s: &Stmt) { SawStmt(saw_stmt(&s.node)).hash(self.st); visit::walk_stmt(self, s) } - fn visit_view_item(&mut self, i: &ViewItem) { - // Two kinds of view items can affect the ABI for a crate: - // exported `pub use` view items (since that may expose - // items that downstream crates can call), and `use - // foo::Trait`, since changing that may affect method - // resolution. - // - // The simplest approach to handling both of the above is - // just to adopt the same simple-minded (fine-grained) - // hash that I am deploying elsewhere here. - SawViewItem.hash(self.st); visit::walk_view_item(self, i) - } - fn visit_foreign_item(&mut self, i: &ForeignItem) { // FIXME (#14132) ideally we would incorporate privacy (or // perhaps reachability) somewhere here, so foreign items -- 2.44.0