diff options
author | Alan Wu <XrXr@users.noreply.github.com> | 2022-11-17 17:33:18 -0500 |
---|---|---|
committer | Alan Wu <XrXr@users.noreply.github.com> | 2022-11-25 16:21:40 -0500 |
commit | 790cf4b6d0475614afb127b416e87cfa39044d67 (patch) | |
tree | d04089ae209b4c3b27b6ab68097a6065d3583520 /memory_view.c | |
parent | e15cd01149afe4924460f81cb6e27dd96de06657 (diff) | |
download | ruby-790cf4b6d0475614afb127b416e87cfa39044d67.tar.gz |
Fix autoload status of statically linked extensions
Previously, for statically-linked extensions, we used
`vm->loading_table` to delay calling the init function until the
extensions are required. This caused the extensions to look like they
are in the middle of being loaded even before they're required.
(`rb_feature_p()` returned true with a loading path output.) Combined
with autoload, queries like `defined?(CONST)` and `Module#autoload?`
were confused by this and returned nil incorrectly. RubyGems uses
`defined?` to detect if OpenSSL is available and failed when OpenSSL was
available in builds using `--with-static-linked-ext`.
Use a dedicated table for the init functions instead of adding them to
the loading table. This lets us remove some logic from non-EXTSTATIC
builds.
[Bug #19115]
Diffstat (limited to 'memory_view.c')
0 files changed, 0 insertions, 0 deletions