https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/assets/favicon-0e291875.ico2026-03-11T11:52:00ZRuby Issue Tracking Systemhttps://bugs.ruby-lang.org/issues/21951?journal_id=1166752026-03-11T11:52:00Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org <ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Backport</strong> deleted (<del><i>3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN</i></del>)</li></ul> https://bugs.ruby-lang.org/issues/21951?journal_id=1167062026-03-16T06:40:42Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org <ul><li><strong>Subject</strong> changed from <i>Lazy load error enhancer gems to speed up boot time</i> to <i>Lazy load error extension gems to speed up boot time</i></li></ul> https://bugs.ruby-lang.org/issues/21951?journal_id=1167692026-03-18T06:31:42Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org <ul></ul><p>Some libraries implicitly depend on <code>did_you_mean</code> and other gems being loaded at boot, calling their class methods (e.g., <code>DidYouMean::SpellChecker</code>) without an explicit <code>require</code>.</p> <p>I tried to switch from a simple deferred <code>require</code> approach to using <code>autoload</code>. Unfortunately, when using <code>autoload</code> for lazy loading of them, some Ractor btests is failed with YJIT/ZJIT.</p> <ul> <li><a href="https://github.com/ruby/ruby/actions/runs/23230199826/job/67521873278?pr=16371" class="external">https://github.com/ruby/ruby/actions/runs/23230199826/job/67521873278?pr=16371</a></li> <li><a href="https://github.com/ruby/ruby/actions/runs/23230199813/job/67521873227?pr=16371" class="external">https://github.com/ruby/ruby/actions/runs/23230199813/job/67521873227?pr=16371</a></li> </ul> <p>Does anyone know that causes?</p>