A-lintL-restrictiongood first issue
Repository metrics
- Stars
- (10,406 stars)
- PR merge metrics
- (Avg merge 19d 22h) (113 merged PRs in 30d)
Description
I think there should be a warning about the wildcard pattern in let.
I can't imagine any situation where this makes sense, and there are cases where it's a mistake caused by taking _ for identifier though it's not.
Wrong:
{
let _ = my scope guard or whatever
// dropped right away
do stuff
}
Correct:
{
let _g = my scope guard or whatever
do stuff
// dropped at the end of the scope
}