[#113435] [Ruby master Feature#19634] Pattern matching dynamic key — "baweaver (Brandon Weaver) via ruby-core" <ruby-core@...>
Issue #19634 has been reported by baweaver (Brandon Weaver).
6 messages
2023/05/09
[#113489] [Ruby master Bug#19642] Remove vectored read/write from `io.c`. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>
Issue #19642 has been reported by ioquatix (Samuel Williams).
10 messages
2023/05/15
[ruby-core:113537] [Ruby master Feature#19644] Module::current to complement Module::nesting
From:
"bughit (bug hit) via ruby-core" <ruby-core@...>
Date:
2023-05-19 18:19:36 UTC
List:
ruby-core #113537
Issue #19644 has been updated by bughit (bug hit). Eregon (Benoit Daloze) wrote in #note-1: > Is `self` not enough? This needs a concrete use case. `Module::nesting[0]` is the current lexically open module/class, its not `self` ---------------------------------------- Feature #19644: Module::current to complement Module::nesting https://bugs.ruby-lang.org/issues/19644#change-103165 * Author: bughit (bug hit) * Status: Open * Priority: Normal ---------------------------------------- Module::current == Module::nesting[0] but without needlessly walking the entire nesting hierarchy. Could be useful for debugging/logging. It could also be a Kernel global (like __method__) or a keyword (like __FILE__) -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- [email protected] To unsubscribe send an email to [email protected] ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/