'#executables' method inside Gem::Specification appears to be non-idempotent. Is this intentional?

[impostorsguides]

I use RBENV to manage my Ruby versions, and while spelunking in the codebase, I found its rubygems_plugin.rb file. In RBENV's case, the goal of the file appears to be to rebuild RBENV's shims whenever a gem is installed or uninstalled.

This works fine when I'm doing a fresh install of a new gem, but when I run it again, rbenv rehash doesn't execute. On closer inspection, I discovered that it's because installer.spec.executables.any? returns false if the gem was previously installed.

Note- for the purposes of this question, my concern is not with whether their rubygems_plugin.rb uses the #executables method in its intended fashion. I don't believe their usage is incorrect, but I know that if I did, I'd need to post my comments in their repo (not here). I simply mention RBENV as context for how I discovered the behavior of #executables.

I'm still getting familiar with the Gem::Specification code, and I don't yet know where the executables array gets populated. For now, I'm just wondering if this is expected behavior or not. If so, I'd be genuinely curious to learn about the purpose of leaving it empty on subsequent installations.

Thanks, I love RubyGems and I appreciate the core team's hard work. 👍

EDIT- I'm using RubyGems v3.1.6.

[impostorsguides]

Update- this was user error on my part. I neglected to check the value of installer.spec.name on each install attempt. The executables that I observed on the first pass were for a dependency of the gem in question, not the gem itself. This dependency was not installed again on subsequent passes, therefore I saw a non-empty executables array on the first install and an empty array on subsequent attempts. My apologies.