Sha256: 8fc628acc663b282fb58093397dc83c44d80d3a8e213221a1698e54df8141fed
Contents?: true
Size: 1.81 KB
Versions: 2
Compression:
Stored size: 1.81 KB
Contents
# frozen_string_literal: true module RuboCop module Cop module Performance # This cop identifies uses of `Range#include?` and `Range#member?`, which iterates over each # item in a `Range` to see if a specified item is there. In contrast, # `Range#cover?` simply compares the target item with the beginning and # end points of the `Range`. In a great majority of cases, this is what # is wanted. # # This cop is `Safe: false` by default because `Range#include?` (or `Range#member?`) and # `Range#cover?` are not equivalent behaviour. # # @example # # bad # ('a'..'z').include?('b') # => true # ('a'..'z').member?('b') # => true # # # good # ('a'..'z').cover?('b') # => true # # # Example of a case where `Range#cover?` may not provide # # the desired result: # # ('a'..'z').cover?('yellow') # => true class RangeInclude < Cop MSG = 'Use `Range#cover?` instead of `Range#%<bad_method>s`.' # TODO: If we traced out assignments of variables to their uses, we # might pick up on a few more instances of this issue # Right now, we only detect direct calls on a Range literal # (We don't even catch it if the Range is in double parens) def_node_matcher :range_include, <<~PATTERN (send {irange erange (begin {irange erange})} ${:include? :member?} ...) PATTERN def on_send(node) range_include(node) do |bad_method| message = format(MSG, bad_method: bad_method) add_offense(node, location: :selector, message: message) end end def autocorrect(node) ->(corrector) { corrector.replace(node.loc.selector, 'cover?') } end end end end end
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
rubocop-performance-1.7.1 | lib/rubocop/cop/performance/range_include.rb |
rubocop-performance-1.7.0 | lib/rubocop/cop/performance/range_include.rb |