[#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:113558] [Ruby master Feature#19644] Module::current to complement Module::nesting
From:
"Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>
Date:
2023-05-20 12:41:48 UTC
List:
ruby-core #113558
Issue #19644 has been updated by Eregon (Benoit Daloze). Status changed from Open to Rejected > Could be useful for debugging/logging. Those are not performance critical, so `Module::nesting[0]` is enough. You also don't want to provide a concrete example where it's a clear gain, OK, let's close then until there is a clear use case for it where `Module::nesting[0]` is not enough. ---------------------------------------- Feature #19644: Module::current to complement Module::nesting https://bugs.ruby-lang.org/issues/19644#change-103189 * Author: bughit (bug hit) * Status: Rejected * 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 -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/