2022-04-07 12:39:59 -05:00
|
|
|
use clippy_utils::diagnostics::{span_lint_and_help, span_lint_and_note};
|
|
|
|
use clippy_utils::is_must_use_func_call;
|
|
|
|
use clippy_utils::ty::{is_copy, is_must_use_ty, is_type_lang_item};
|
|
|
|
use rustc_hir::{Expr, ExprKind, LangItem};
|
2020-01-12 00:08:41 -06:00
|
|
|
use rustc_lint::{LateContext, LateLintPass};
|
2020-01-11 05:37:08 -06:00
|
|
|
use rustc_session::{declare_lint_pass, declare_tool_lint};
|
2022-02-26 07:26:21 -06:00
|
|
|
use rustc_span::sym;
|
2016-02-01 12:53:03 -06: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 calls to `std::mem::drop` with a reference
|
2019-03-05 10:50:33 -06:00
|
|
|
/// instead of an owned value.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `drop` on a reference will only drop the
|
2019-03-05 10:50:33 -06:00
|
|
|
/// reference itself, which is a no-op. It will not call the `drop` method (from
|
|
|
|
/// the `Drop` trait implementation) on the underlying referenced value, which
|
|
|
|
/// is likely what was intended.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2019-03-05 16:23:50 -06:00
|
|
|
/// ```ignore
|
2019-03-05 10:50:33 -06:00
|
|
|
/// let mut lock_guard = mutex.lock();
|
|
|
|
/// std::mem::drop(&lock_guard) // Should have been drop(lock_guard), mutex
|
|
|
|
/// // still locked
|
|
|
|
/// operation_that_requires_mutex_to_be_unlocked();
|
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2016-08-06 03:18:36 -05:00
|
|
|
pub DROP_REF,
|
2018-03-28 08:24:26 -05:00
|
|
|
correctness,
|
2016-08-06 03:18:36 -05:00
|
|
|
"calls to `std::mem::drop` with a reference instead of an owned value"
|
2016-02-05 17:13:29 -06:00
|
|
|
}
|
2016-02-01 12:53:03 -06: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 calls to `std::mem::forget` with a reference
|
2019-03-05 10:50:33 -06:00
|
|
|
/// instead of an owned value.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `forget` on a reference will only forget the
|
2019-03-05 10:50:33 -06:00
|
|
|
/// reference itself, which is a no-op. It will not forget the underlying
|
|
|
|
/// referenced
|
|
|
|
/// value, which is likely what was intended.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```rust
|
|
|
|
/// let x = Box::new(1);
|
|
|
|
/// std::mem::forget(&x) // Should have been forget(x), x will still be dropped
|
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2016-12-29 21:43:22 -06:00
|
|
|
pub FORGET_REF,
|
2018-03-28 08:24:26 -05:00
|
|
|
correctness,
|
2016-12-29 21:43:22 -06:00
|
|
|
"calls to `std::mem::forget` with a reference instead of an owned value"
|
|
|
|
}
|
|
|
|
|
2018-03-28 08:24:26 -05:00
|
|
|
declare_clippy_lint! {
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### What it does
|
|
|
|
/// Checks for calls to `std::mem::drop` with a value
|
2019-03-05 10:50:33 -06:00
|
|
|
/// that derives the Copy trait
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `std::mem::drop` [does nothing for types that
|
2019-03-05 10:50:33 -06:00
|
|
|
/// implement Copy](https://doc.rust-lang.org/std/mem/fn.drop.html), since the
|
|
|
|
/// value will be copied and moved into the function on invocation.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```rust
|
|
|
|
/// let x: i32 = 42; // i32 implements Copy
|
|
|
|
/// std::mem::drop(x) // A copy of x is passed to the function, leaving the
|
|
|
|
/// // original unaffected
|
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2017-02-26 20:32:41 -06:00
|
|
|
pub DROP_COPY,
|
2018-03-28 08:24:26 -05:00
|
|
|
correctness,
|
2017-02-26 20:32:41 -06:00
|
|
|
"calls to `std::mem::drop` with a value that implements Copy"
|
|
|
|
}
|
|
|
|
|
2018-03-28 08:24:26 -05:00
|
|
|
declare_clippy_lint! {
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### What it does
|
|
|
|
/// Checks for calls to `std::mem::forget` with a value that
|
2019-03-05 10:50:33 -06:00
|
|
|
/// derives the Copy trait
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `std::mem::forget` [does nothing for types that
|
2019-03-05 10:50:33 -06:00
|
|
|
/// implement Copy](https://doc.rust-lang.org/std/mem/fn.drop.html) since the
|
|
|
|
/// value will be copied and moved into the function on invocation.
|
|
|
|
///
|
|
|
|
/// An alternative, but also valid, explanation is that Copy types do not
|
|
|
|
/// implement
|
|
|
|
/// the Drop trait, which means they have no destructors. Without a destructor,
|
|
|
|
/// there
|
|
|
|
/// is nothing for `std::mem::forget` to ignore.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```rust
|
|
|
|
/// let x: i32 = 42; // i32 implements Copy
|
|
|
|
/// std::mem::forget(x) // A copy of x is passed to the function, leaving the
|
|
|
|
/// // original unaffected
|
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2017-02-26 20:32:41 -06:00
|
|
|
pub FORGET_COPY,
|
2018-03-28 08:24:26 -05:00
|
|
|
correctness,
|
2017-02-26 20:32:41 -06:00
|
|
|
"calls to `std::mem::forget` with a value that implements Copy"
|
|
|
|
}
|
|
|
|
|
2022-04-07 12:39:59 -05:00
|
|
|
declare_clippy_lint! {
|
|
|
|
/// ### What it does
|
|
|
|
/// Checks for calls to `std::mem::drop` with a value that does not implement `Drop`.
|
|
|
|
///
|
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `std::mem::drop` is no different than dropping such a type. A different value may
|
|
|
|
/// have been intended.
|
|
|
|
///
|
|
|
|
/// ### Example
|
|
|
|
/// ```rust
|
|
|
|
/// struct Foo;
|
|
|
|
/// let x = Foo;
|
|
|
|
/// std::mem::drop(x);
|
|
|
|
/// ```
|
2022-07-18 02:39:37 -05:00
|
|
|
#[clippy::version = "1.62.0"]
|
2022-04-07 12:39:59 -05:00
|
|
|
pub DROP_NON_DROP,
|
|
|
|
suspicious,
|
|
|
|
"call to `std::mem::drop` with a value which does not implement `Drop`"
|
|
|
|
}
|
|
|
|
|
|
|
|
declare_clippy_lint! {
|
|
|
|
/// ### What it does
|
|
|
|
/// Checks for calls to `std::mem::forget` with a value that does not implement `Drop`.
|
|
|
|
///
|
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Calling `std::mem::forget` is no different than dropping such a type. A different value may
|
|
|
|
/// have been intended.
|
|
|
|
///
|
|
|
|
/// ### Example
|
|
|
|
/// ```rust
|
|
|
|
/// struct Foo;
|
|
|
|
/// let x = Foo;
|
|
|
|
/// std::mem::forget(x);
|
|
|
|
/// ```
|
2022-07-18 02:39:37 -05:00
|
|
|
#[clippy::version = "1.62.0"]
|
2022-04-07 12:39:59 -05:00
|
|
|
pub FORGET_NON_DROP,
|
|
|
|
suspicious,
|
|
|
|
"call to `std::mem::forget` with a value which does not implement `Drop`"
|
|
|
|
}
|
|
|
|
|
|
|
|
declare_clippy_lint! {
|
|
|
|
/// ### What it does
|
|
|
|
/// Prevents the safe `std::mem::drop` function from being called on `std::mem::ManuallyDrop`.
|
|
|
|
///
|
|
|
|
/// ### Why is this bad?
|
|
|
|
/// The safe `drop` function does not drop the inner value of a `ManuallyDrop`.
|
|
|
|
///
|
|
|
|
/// ### Known problems
|
|
|
|
/// Does not catch cases if the user binds `std::mem::drop`
|
|
|
|
/// to a different name and calls it that way.
|
|
|
|
///
|
|
|
|
/// ### Example
|
|
|
|
/// ```rust
|
|
|
|
/// struct S;
|
|
|
|
/// drop(std::mem::ManuallyDrop::new(S));
|
|
|
|
/// ```
|
|
|
|
/// Use instead:
|
|
|
|
/// ```rust
|
|
|
|
/// struct S;
|
|
|
|
/// unsafe {
|
|
|
|
/// std::mem::ManuallyDrop::drop(&mut std::mem::ManuallyDrop::new(S));
|
|
|
|
/// }
|
|
|
|
/// ```
|
|
|
|
#[clippy::version = "1.49.0"]
|
|
|
|
pub UNDROPPED_MANUALLY_DROPS,
|
|
|
|
correctness,
|
|
|
|
"use of safe `std::mem::drop` function to drop a std::mem::ManuallyDrop, which will not drop the inner value"
|
|
|
|
}
|
|
|
|
|
2017-03-24 04:21:12 -05:00
|
|
|
const DROP_REF_SUMMARY: &str = "calls to `std::mem::drop` with a reference instead of an owned value. \
|
2021-03-12 08:30:50 -06:00
|
|
|
Dropping a reference does nothing";
|
2017-03-24 04:21:12 -05:00
|
|
|
const FORGET_REF_SUMMARY: &str = "calls to `std::mem::forget` with a reference instead of an owned value. \
|
2021-03-12 08:30:50 -06:00
|
|
|
Forgetting a reference does nothing";
|
2020-01-06 00:30:43 -06:00
|
|
|
const DROP_COPY_SUMMARY: &str = "calls to `std::mem::drop` with a value that implements `Copy`. \
|
2021-03-12 08:30:50 -06:00
|
|
|
Dropping a copy leaves the original intact";
|
2020-01-06 00:30:43 -06:00
|
|
|
const FORGET_COPY_SUMMARY: &str = "calls to `std::mem::forget` with a value that implements `Copy`. \
|
2021-03-12 08:30:50 -06:00
|
|
|
Forgetting a copy leaves the original intact";
|
2022-04-07 12:39:59 -05:00
|
|
|
const DROP_NON_DROP_SUMMARY: &str = "call to `std::mem::drop` with a value that does not implement `Drop`. \
|
2022-05-05 09:12:52 -05:00
|
|
|
Dropping such a type only extends its contained lifetimes";
|
2022-04-07 12:39:59 -05:00
|
|
|
const FORGET_NON_DROP_SUMMARY: &str = "call to `std::mem::forget` with a value that does not implement `Drop`. \
|
|
|
|
Forgetting such a type is the same as dropping it";
|
2017-02-26 20:32:41 -06:00
|
|
|
|
2022-04-07 12:39:59 -05:00
|
|
|
declare_lint_pass!(DropForgetRef => [
|
|
|
|
DROP_REF,
|
|
|
|
FORGET_REF,
|
|
|
|
DROP_COPY,
|
|
|
|
FORGET_COPY,
|
|
|
|
DROP_NON_DROP,
|
|
|
|
FORGET_NON_DROP,
|
|
|
|
UNDROPPED_MANUALLY_DROPS
|
|
|
|
]);
|
2016-02-01 12:53:03 -06:00
|
|
|
|
2020-06-25 15:41:36 -05:00
|
|
|
impl<'tcx> LateLintPass<'tcx> for DropForgetRef {
|
|
|
|
fn check_expr(&mut self, cx: &LateContext<'tcx>, expr: &'tcx Expr<'_>) {
|
2022-04-07 12:39:59 -05:00
|
|
|
if let ExprKind::Call(path, [arg]) = expr.kind
|
|
|
|
&& let ExprKind::Path(ref qpath) = path.kind
|
|
|
|
&& let Some(def_id) = cx.qpath_res(qpath, path.hir_id).opt_def_id()
|
|
|
|
&& let Some(fn_name) = cx.tcx.get_diagnostic_name(def_id)
|
|
|
|
{
|
|
|
|
let arg_ty = cx.typeck_results().expr_ty(arg);
|
|
|
|
let (lint, msg) = match fn_name {
|
|
|
|
sym::mem_drop if arg_ty.is_ref() => (DROP_REF, DROP_REF_SUMMARY),
|
|
|
|
sym::mem_forget if arg_ty.is_ref() => (FORGET_REF, FORGET_REF_SUMMARY),
|
|
|
|
sym::mem_drop if is_copy(cx, arg_ty) => (DROP_COPY, DROP_COPY_SUMMARY),
|
|
|
|
sym::mem_forget if is_copy(cx, arg_ty) => (FORGET_COPY, FORGET_COPY_SUMMARY),
|
|
|
|
sym::mem_drop if is_type_lang_item(cx, arg_ty, LangItem::ManuallyDrop) => {
|
|
|
|
span_lint_and_help(
|
|
|
|
cx,
|
|
|
|
UNDROPPED_MANUALLY_DROPS,
|
|
|
|
expr.span,
|
|
|
|
"the inner value of this ManuallyDrop will not be dropped",
|
|
|
|
None,
|
|
|
|
"to drop a `ManuallyDrop<T>`, use std::mem::ManuallyDrop::drop",
|
|
|
|
);
|
|
|
|
return;
|
2017-02-26 20:32:41 -06:00
|
|
|
}
|
2022-04-07 12:39:59 -05:00
|
|
|
sym::mem_drop
|
|
|
|
if !(arg_ty.needs_drop(cx.tcx, cx.param_env)
|
|
|
|
|| is_must_use_func_call(cx, arg)
|
|
|
|
|| is_must_use_ty(cx, arg_ty)) =>
|
|
|
|
{
|
|
|
|
(DROP_NON_DROP, DROP_NON_DROP_SUMMARY)
|
|
|
|
},
|
|
|
|
sym::mem_forget if !arg_ty.needs_drop(cx.tcx, cx.param_env) => {
|
|
|
|
(FORGET_NON_DROP, FORGET_NON_DROP_SUMMARY)
|
|
|
|
},
|
|
|
|
_ => return,
|
|
|
|
};
|
|
|
|
span_lint_and_note(
|
|
|
|
cx,
|
|
|
|
lint,
|
|
|
|
expr.span,
|
|
|
|
msg,
|
|
|
|
Some(arg.span),
|
|
|
|
&format!("argument has type `{}`", arg_ty),
|
|
|
|
);
|
2017-10-23 14:18:02 -05:00
|
|
|
}
|
2016-02-01 12:53:03 -06:00
|
|
|
}
|
|
|
|
}
|