https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-09-27T09:47:44ZRuby Issue Tracking SystemRuby master - Feature #18227: Static class initialization.https://bugs.ruby-lang.org/issues/18227?journal_id=938912021-09-27T09:47:44ZEregon (Benoit Daloze)
<ul></ul><p>I think for the public API functions should be used, as that providees a lot more flexibility in implementation.<br>
Initializing as static means there is no possibility to ever add e.g. some context argument to it, so it is limiting.</p> Ruby master - Feature #18227: Static class initialization.https://bugs.ruby-lang.org/issues/18227?journal_id=939052021-09-27T21:58:44Zioquatix (Samuel Williams)samuel@oriontransfer.net
<ul></ul><p>Yes, this would only be for internal CRuby initialization, not for 3rd party code.</p> Ruby master - Feature #18227: Static class initialization.https://bugs.ruby-lang.org/issues/18227?journal_id=939452021-09-29T21:21:29Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Backport</strong> deleted (<del><i>2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN</i></del>)</li></ul>