Expected behavior

rubocop --help lists command: --disable-pending-cops
And invoking rubocop with that option does what it says it does.

Actual behavior

rubocop --disable-p will also disable the pending cops.
rubocop --disable- or less will yield ambiguous option: --disable-

It looks like rubocop is using substring matches for all command line options?
Its kinda convenient to only type --disable-pending instead of the full option.
But this seems weird, I would assume any unrecognized options should throw an error, but I guess maybe this is intended and not a bug?

RuboCop version

rubocop -V
1.57.1 (using Parser 3.2.2.4, rubocop-ast 1.29.0, running on ruby 2.7.8) [x86_64-darwin21]
  - rubocop-performance 1.19.1
  - rubocop-rails 2.21.2