Bug #21828: An incorrect warning message related to `benchmark` is shown when using `benchmark-ips`

• Status: Closed
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -
• ruby -v: ruby 4.0.0 (2025-12-25 revision 553f1675f3) +PRISM [x86_64-linux]
• Backport: 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONTNEED, 4.0: REQUIRED

[y-yagi (Yuji Yaginuma)]

Descrition

When using benchmark-ips gem with Ruby 4.0.0, the warning related to benchmark gem is shown.

Step to reproduce

# Gemfile
# frozen_string_literal: true

source "https://rubygems.org"

gem "benchmark-ips"

# script.rb
require "benchmark/ips"

$ bundle exec ruby -v script.rb
ruby 4.0.0 (2025-12-25 revision 553f1675f3) +PRISM [x86_64-linux]
script.rb:1: warning: benchmark/ips is found in benchmark, which is not part of the default gems since Ruby 4.0.0.
You can add benchmark to your Gemfile or gemspec to fix this error.

Expected behavior

The warning for benchmark isn't shown when using benchmark-ips.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee set to hsbt (Hiroshi SHIBATA)

[khasinski (Krzysztof Hasiński)]

• Status changed from Assigned to Closed

Applied in changeset git|768862868472fb1800e556effb0e37be2fbaec52.

---

Fix incorrect bundled gems warning for hyphenated gem names

When requiring a file like "benchmark/ips", the warning system would
incorrectly warn about the "benchmark" gem not being a default gem,
even when the user has "benchmark-ips" (a separate third-party gem)
in their Gemfile.

The fix checks if a hyphenated version of the require path exists in
the bundle specs before issuing a warning. For example, requiring
"benchmark/ips" now checks for both "benchmark" and "benchmark-ips"
in the Gemfile.

[Bug #21828]

[hsbt (Hiroshi SHIBATA)]

• Backport changed from 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN to 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONTNEED, 4.0: REQUIRED

https://github.com/ruby/ruby/pull/15824