Module eager_or_lazy 

Utilities for evaluating whether eagerly evaluated expressions can be made lazy and vice versa.

Things to consider:

• does the expression have side-effects?
• is the expression computationally expensive?

See lints:

• unnecessary-lazy-evaluations
• or-fun-call
• option-if-let-else

Re-exports

use crate::consts::ConstEvalCtxt; 🔒

use crate::consts::FullInt; 🔒

use crate::sym; 🔒

use crate::ty::all_clauses_of; 🔒

use crate::visitors::is_const_evaluatable; 🔒

use rustc_hir::def::DefKind; 🔒

use rustc_hir::def::Res; 🔒

use rustc_hir::def_id::DefId; 🔒

use rustc_hir::intravisit::Visitor; 🔒

use rustc_hir::intravisit::walk_expr; 🔒

use rustc_hir::BinOpKind; 🔒

use rustc_hir::Block; 🔒

use rustc_hir::Expr; 🔒

use rustc_hir::ExprKind; 🔒

use rustc_hir::QPath; 🔒

use rustc_hir::UnOp; 🔒

use rustc_lint::LateContext; 🔒

use rustc_middle::ty::adjustment::Adjust; 🔒

use rustc_middle::ty::adjustment::DerefAdjustKind; 🔒

use rustc_middle::ty; 🔒

use rustc_middle::ty::TyCtxt; 🔒

use rustc_span::Symbol; 🔒

use std::cmp; 🔒

use std::ops; 🔒

Enums

EagernessSuggestion 🔒

Functions

expr_eagerness 🔒

fn_eagerness 🔒

Determine the eagerness of the given function call.

res_has_significant_drop 🔒

switch_to_eager_eval

Whether the given expression should be changed to evaluate eagerly

switch_to_lazy_eval

Whether the given expression should be changed to evaluate lazily