Perl::Critic::Policy::BuiltinFunctions::ProhibitBooleanGrep(3pm)

Perl::Critic::Policy::BuiltinFunctions::ProhibitBooleanGrep3pm

Use "any" from "list::util", "list::someutils", or "list::moreutils" instead of "grep" in boolean context.

Affiliation

This Policy is part of the core Perl::Critic distribution.

Overview

Using "grep" in boolean context is a common idiom for checking if any elements in a list match a condition. This works because boolean context is a subset of scalar context, and grep returns the number of matches in scalar context. A non-zero number of matches means a match.

But consider the case of a long array where the first element is a match. Boolean "grep" still checks all of the rest of the elements needlessly. Instead, a better solution is to use the "any" function from either List::Util, List::SomeUtils, or List::MoreUtils. The "any" function will return as soon as a successful match is found, rather than processing the entire list. This saves time.

Configuration

This Policy is not configurable except for the standard options.

Caveats

The algorithm for detecting boolean context takes a LOT of shortcuts. There are lots of known false negatives. But, I was conservative in writing this, so I hope there are no false positives.

Credits

Initial development of this policy was supported by a grant from the Perl Foundation.

Releases

10 releases since Debian 5.0 (Lenny); the text changed 9 times.

  1. 5.0
  2. 6.0
  3. 7
  4. 8
  5. 9
  6. 10
  7. 11
  8. 12
  9. 13
  10. Arch

Author

Chris Dolan <[email protected]>

From perl-perl-critic 1.156-3 in Arch Linux 2026-11-01. Parsed by carta from the page's man source.