/// them leads to more readable code.
///
/// **Known problems:** Potential false negatives: we bail out if the function
- /// has a where-clause where lifetimes are mentioned.
+ /// has a `where` clause where lifetimes are mentioned.
///
/// **Example:**
/// ```rust
self.collect_anonymous_lifetimes(path, ty);
},
TyKind::Def(item, _) => {
- if let ItemKind::Existential(ref exist_ty) = self.cx.tcx.hir().expect_item(item.id).node {
+ let map = self.cx.tcx.hir();
+ if let ItemKind::Existential(ref exist_ty) = map.expect_item(map.hir_to_node_id(item.id)).node {
for bound in &exist_ty.bounds {
if let GenericBound::Outlives(_) = *bound {
self.record(&None);
}
}
-/// Are any lifetimes mentioned in the where-clause? If yes, we don't try to
+/// Are any lifetimes mentioned in the `where` clause? If so, we don't try to
/// reason about elision.
fn has_where_lifetimes<'a, 'tcx: 'a>(cx: &LateContext<'a, 'tcx>, where_clause: &'tcx WhereClause) -> bool {
for predicate in &where_clause.predicates {