2018-05-30 03:15:50 -05:00
|
|
|
use crate::consts::{constant_simple, Constant};
|
|
|
|
use crate::utils::span_help_and_lint;
|
2018-11-27 14:14:15 -06:00
|
|
|
use if_chain::if_chain;
|
2018-12-29 09:04:45 -06:00
|
|
|
use rustc::hir::*;
|
|
|
|
use rustc::lint::{LateContext, LateLintPass, LintArray, LintPass};
|
2019-04-08 15:43:55 -05:00
|
|
|
use rustc::{declare_lint_pass, declare_tool_lint};
|
2015-10-11 21:22:13 -05:00
|
|
|
|
2018-03-28 08:24:26 -05:00
|
|
|
declare_clippy_lint! {
|
2019-03-05 10:50:33 -06:00
|
|
|
/// **What it does:** Checks for `0.0 / 0.0`.
|
|
|
|
///
|
|
|
|
/// **Why is this bad?** It's less readable than `std::f32::NAN` or
|
|
|
|
/// `std::f64::NAN`.
|
|
|
|
///
|
|
|
|
/// **Known problems:** None.
|
|
|
|
///
|
|
|
|
/// **Example:**
|
|
|
|
/// ```rust
|
2019-08-02 01:13:54 -05:00
|
|
|
/// 0.0f32 / 0.0;
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```
|
2016-02-05 17:13:29 -06:00
|
|
|
pub ZERO_DIVIDED_BY_ZERO,
|
2018-03-28 08:24:26 -05:00
|
|
|
complexity,
|
2016-02-05 17:13:29 -06:00
|
|
|
"usage of `0.0 / 0.0` to obtain NaN instead of std::f32::NaN or std::f64::NaN"
|
|
|
|
}
|
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
|
|
|
|
2019-04-08 15:43:55 -05:00
|
|
|
impl<'a, 'tcx> LateLintPass<'a, 'tcx> for ZeroDiv {
|
2016-12-07 06:13:40 -06:00
|
|
|
fn check_expr(&mut self, cx: &LateContext<'a, 'tcx>, expr: &'tcx Expr) {
|
2015-10-11 21:22:13 -05:00
|
|
|
// check for instances of 0.0/0.0
|
2017-10-23 14:18:02 -05:00
|
|
|
if_chain! {
|
2018-07-12 02:30:57 -05:00
|
|
|
if let ExprKind::Binary(ref op, ref left, ref right) = expr.node;
|
2018-07-12 02:50:09 -05:00
|
|
|
if let BinOpKind::Div = op.node;
|
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.
|
2018-05-13 06:16:31 -05:00
|
|
|
if let Some(lhs_value) = constant_simple(cx, cx.tables, left);
|
|
|
|
if let Some(rhs_value) = constant_simple(cx, cx.tables, right);
|
2018-03-13 05:38:11 -05:00
|
|
|
if Constant::F32(0.0) == lhs_value || Constant::F64(0.0) == lhs_value;
|
|
|
|
if Constant::F32(0.0) == rhs_value || Constant::F64(0.0) == rhs_value;
|
2017-10-23 14:18:02 -05:00
|
|
|
then {
|
|
|
|
// since we're about to suggest a use of std::f32::NaN or std::f64::NaN,
|
|
|
|
// match the precision of the literals that are given.
|
2018-03-13 05:38:11 -05:00
|
|
|
let float_type = match (lhs_value, rhs_value) {
|
|
|
|
(Constant::F64(_), _)
|
|
|
|
| (_, Constant::F64(_)) => "f64",
|
2017-10-23 14:18:02 -05:00
|
|
|
_ => "f32"
|
|
|
|
};
|
2017-11-04 14:56:05 -05:00
|
|
|
span_help_and_lint(
|
|
|
|
cx,
|
|
|
|
ZERO_DIVIDED_BY_ZERO,
|
|
|
|
expr.span,
|
2017-10-23 14:18:02 -05:00
|
|
|
"constant division of 0.0 with 0.0 will always result in NaN",
|
2017-11-04 14:56:05 -05:00
|
|
|
&format!(
|
|
|
|
"Consider using `std::{}::NAN` if you would like a constant representing NaN",
|
|
|
|
float_type,
|
|
|
|
),
|
|
|
|
);
|
2017-10-23 14:18:02 -05:00
|
|
|
}
|
|
|
|
}
|
2015-10-11 21:22:13 -05:00
|
|
|
}
|
|
|
|
}
|