Ticks around std::mem::forget

This commit is contained in:
Taylor Cramer 2016-04-20 13:33:05 -07:00
parent 7961f59303
commit 12ae306630
2 changed files with 2 additions and 2 deletions

View File

@ -85,7 +85,7 @@ name
[match_overlapping_arm](https://github.com/Manishearth/rust-clippy/wiki#match_overlapping_arm) | warn | a match has overlapping arms
[match_ref_pats](https://github.com/Manishearth/rust-clippy/wiki#match_ref_pats) | warn | a match or `if let` has all arms prefixed with `&`; the match expression can be dereferenced instead
[match_same_arms](https://github.com/Manishearth/rust-clippy/wiki#match_same_arms) | warn | `match` with identical arm bodies
[mem_forget](https://github.com/Manishearth/rust-clippy/wiki#mem_forget) | allow | std::mem::forget usage is likely to cause memory leaks
[mem_forget](https://github.com/Manishearth/rust-clippy/wiki#mem_forget) | allow | `std::mem::forget` usage is likely to cause memory leaks
[min_max](https://github.com/Manishearth/rust-clippy/wiki#min_max) | warn | `min(_, max(_, _))` (or vice versa) with bounds clamping the result to a constant
[modulo_one](https://github.com/Manishearth/rust-clippy/wiki#modulo_one) | warn | taking a number modulo 1, which always returns 0
[mut_mut](https://github.com/Manishearth/rust-clippy/wiki#mut_mut) | allow | usage of double-mut refs, e.g. `&mut &mut ...` (either copy'n'paste error, or shows a fundamental misunderstanding of references)

View File

@ -12,7 +12,7 @@ use utils::{match_def_path, paths, span_lint};
declare_lint! {
pub MEM_FORGET,
Allow,
"std::mem::forget usage is likely to cause memory leaks"
"`std::mem::forget` usage is likely to cause memory leaks"
}
pub struct MemForget;