2021-06-03 01:41:37 -05:00
|
|
|
use clippy_utils::consts::{constant_simple, Constant};
|
2021-03-25 13:29:11 -05:00
|
|
|
use clippy_utils::diagnostics::span_lint_and_help;
|
2020-02-21 02:39:38 -06:00
|
|
|
use rustc_hir::{BinOpKind, Expr, ExprKind};
|
2020-01-12 00:08:41 -06:00
|
|
|
use rustc_lint::{LateContext, LateLintPass};
|
2023-12-01 11:21:58 -06:00
|
|
|
use rustc_session::declare_lint_pass;
|
2015-10-11 21:22:13 -05:00
|
|
|
|
2018-03-28 08:24:26 -05:00
|
|
|
declare_clippy_lint! {
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### What it does
|
|
|
|
/// Checks for `0.0 / 0.0`.
|
2019-03-05 10:50:33 -06:00
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// It's less readable than `f32::NAN` or `f64::NAN`.
|
2019-03-05 10:50:33 -06:00
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2023-11-02 11:35:56 -05:00
|
|
|
/// ```no_run
|
2020-06-09 09:36:01 -05:00
|
|
|
/// let nan = 0.0f32 / 0.0;
|
2022-06-16 10:39:06 -05:00
|
|
|
/// ```
|
2020-06-09 09:36:01 -05:00
|
|
|
///
|
2022-06-16 10:39:06 -05:00
|
|
|
/// Use instead:
|
2023-11-02 11:35:56 -05:00
|
|
|
/// ```no_run
|
2020-06-09 09:36:01 -05:00
|
|
|
/// let nan = f32::NAN;
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2016-02-05 17:13:29 -06:00
|
|
|
pub ZERO_DIVIDED_BY_ZERO,
|
2018-03-28 08:24:26 -05:00
|
|
|
complexity,
|
2020-04-07 16:41:00 -05:00
|
|
|
"usage of `0.0 / 0.0` to obtain NaN instead of `f32::NAN` or `f64::NAN`"
|
2016-02-05 17:13:29 -06:00
|
|
|
}
|
2015-10-11 21:22:13 -05:00
|
|
|
|
2019-04-08 15:43:55 -05:00
|
|
|
declare_lint_pass!(ZeroDiv => [ZERO_DIVIDED_BY_ZERO]);
|
2016-08-06 02:55:04 -05:00
|
|
|
|
2020-06-25 15:41:36 -05:00
|
|
|
impl<'tcx> LateLintPass<'tcx> for ZeroDiv {
|
|
|
|
fn check_expr(&mut self, cx: &LateContext<'tcx>, expr: &'tcx Expr<'_>) {
|
2015-10-11 21:22:13 -05:00
|
|
|
// check for instances of 0.0/0.0
|
2023-11-16 12:13:24 -06:00
|
|
|
if let ExprKind::Binary(ref op, left, right) = expr.kind
|
|
|
|
&& op.node == BinOpKind::Div
|
2016-06-05 19:09:19 -05:00
|
|
|
// TODO - constant_simple does not fold many operations involving floats.
|
|
|
|
// That's probably fine for this lint - it's pretty unlikely that someone would
|
|
|
|
// do something like 0.0/(2.0 - 2.0), but it would be nice to warn on that case too.
|
2023-11-16 12:13:24 -06:00
|
|
|
&& let Some(lhs_value) = constant_simple(cx, cx.typeck_results(), left)
|
|
|
|
&& let Some(rhs_value) = constant_simple(cx, cx.typeck_results(), right)
|
|
|
|
&& (Constant::F32(0.0) == lhs_value || Constant::F64(0.0) == lhs_value)
|
|
|
|
&& (Constant::F32(0.0) == rhs_value || Constant::F64(0.0) == rhs_value)
|
|
|
|
{
|
|
|
|
// since we're about to suggest a use of f32::NAN or f64::NAN,
|
|
|
|
// match the precision of the literals that are given.
|
|
|
|
let float_type = match (lhs_value, rhs_value) {
|
|
|
|
(Constant::F64(_), _) | (_, Constant::F64(_)) => "f64",
|
|
|
|
_ => "f32",
|
|
|
|
};
|
|
|
|
span_lint_and_help(
|
|
|
|
cx,
|
|
|
|
ZERO_DIVIDED_BY_ZERO,
|
|
|
|
expr.span,
|
|
|
|
"constant division of `0.0` with `0.0` will always result in NaN",
|
|
|
|
None,
|
|
|
|
&format!("consider using `{float_type}::NAN` if you would like a constant representing NaN",),
|
|
|
|
);
|
2017-10-23 14:18:02 -05:00
|
|
|
}
|
2015-10-11 21:22:13 -05:00
|
|
|
}
|
|
|
|
}
|