Applied in changeset commit:git|2cdfc0d20e5f56b5b45178c172d78d95700666e1. ---------- [Bug #22420] Prefix `lib/` only to collected files of default gems The files collected for a default gem are relative to its lib directory, while the ...ksss (Yuki Kurihara)
The files collected for a default gem are relative to its lib directory, while the files listed by the gemspec itself are relative to the gem root. `load_gemspec` prefixed `lib/` to any `.rb` entry missing from the current directory, so ...ksss (Yuki Kurihara)
Gemspecs can assign local variables such as `files`, `file` and `base`, which overwrote the ones of `load_gemspec`. For instance, ipaddr.gemspec and net-http.gemspec assign `file`, and `loaded_from` of their specs pointed to their Ruby ...ksss (Yuki Kurihara)
The generated RBS files refer to `PP` in `pretty_print: (PP q) -> void`, but `PP` is defined in the `pp` standard library, not in core. Without a declaration, loading the signatures of the prism gem alone fails: $ rbs -r prism valid...ksss (Yuki Kurihara)
Since Ruby 4.0.0, `require "strscan"` loads the default version from rubylibdir even when a newer strscan gem is installed, and does not activate the default gem. If the gem is activated later, its extension is loaded on top of the one a...ksss (Yuki Kurihara)
Sorry for the late reply. I'd like to resume the discussion. I'd like to install the signatures into the gem directory of each default gem, as @Eregon suggested in #note-3: ``` $prefix/lib/ruby/gems/X.Y.0/gems/$name-$version/sig ...ksss (Yuki Kurihara)
The `ruby/rbs` repository consists of type definitions that are loaded by default (`core`) and those that can be loaded optionally (`stdlib`). * Could you please clarify the scope of the type definitions to be migrated? For instance, ...ksss (Yuki Kurihara)
(https://github.com/ruby/strscan/pull/208) I have updated the documentation for `StringScanner#named_captures` to reflect its actual behavior. https://github.com/ruby/strscan/commit/a78da3c025ksss (Yuki Kurihara)