[#113407] [Ruby master Feature#19630] [RFC] Deprecate `Kernel.open("|command-here")` due to frequent security issues — "postmodern (Hal Brodigan) via ruby-core" <ruby-core@...>

Issue #19630 has been reported by postmodern (Hal Brodigan).

19 messages 2023/05/05

[#113430] [Ruby master Feature#19633] Allow passing block to `Kernel#autoload` as alternative to second `filename` argument — "shioyama (Chris Salzberg) via ruby-core" <ruby-core@...>

Issue #19633 has been reported by shioyama (Chris Salzberg).

16 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

[#113498] [Ruby master Feature#19644] Module::current to complement Module::nesting — "bughit (bug hit) via ruby-core" <ruby-core@...>

Issue #19644 has been reported by bughit (bug hit).

12 messages 2023/05/16

[#113517] [Ruby master Misc#19679] Migrate Wiki from bugs.ruby-lang.org to ruby/ruby GitHub repository — "jemmai (Jemma Issroff) via ruby-core" <ruby-core@...>

Issue #19679 has been reported by jemmai (Jemma Issroff).

11 messages 2023/05/18

[#113529] [Ruby master Bug#19681] The final classpath of partially named modules is sometimes inconsistent once permanently named — "byroot (Jean Boussier) via ruby-core" <ruby-core@...>

Issue #19681 has been reported by byroot (Jean Boussier).

34 messages 2023/05/19

[#113538] [Ruby master Feature#19682] ability to get a reference to the "default definee" — "bughit (bug hit) via ruby-core" <ruby-core@...>

Issue #19682 has been reported by bughit (bug hit).

28 messages 2023/05/19

[#113601] [Ruby master Bug#19687] Should a development version of the standard library be included in ruby/ruby? — "jaruga (Jun Aruga) via ruby-core" <ruby-core@...>

Issue #19687 has been reported by jaruga (Jun Aruga).

9 messages 2023/05/23

[#113632] [Ruby master Bug#19691] Case insensitive file systems, require filename casing — "MSP-Greg (Greg L) via ruby-core" <ruby-core@...>

Issue #19691 has been reported by MSP-Greg (Greg L).

7 messages 2023/05/24

[#113656] [Ruby master Misc#19693] Data initialization is significantly slower than Struct — janosch-x via ruby-core <ruby-core@...>

Issue #19693 has been reported by janosch-x (Janosch M=FCller).

13 messages 2023/05/25

[#113660] [Ruby master Feature#19694] Add Regexp#timeout= setter — "aharpole (Aaron Harpole) via ruby-core" <ruby-core@...>

Issue #19694 has been reported by aharpole (Aaron Harpole).

15 messages 2023/05/25

[#113676] [Ruby master Bug#19697] Resolv::DNS resolution for international domains fails with "Encoding::CompatibilityError: incompatible character encodings: UTF-8 and ASCII-8BIT" — "clairity (claire c) via ruby-core" <ruby-core@...>

SXNzdWUgIzE5Njk3IGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGNsYWlyaXR5IChjbGFpcmUgYykuDQ0K

6 messages 2023/05/27

[ruby-core:113641] [Ruby master Feature#19682] ability to get a reference to the "default definee"

From: "rubyFeedback (robert heiler) via ruby-core" <ruby-core@...>
Date: 2023-05-24 18:05:13 UTC
List: ruby-core #113641
Issue #19682 has been updated by rubyFeedback (robert heiler).


bughit wrote:

> "default definee" is quite clear in ruby internals

The internals are not necessarily what ruby "shows" to a user/developer though.

The question here is how a ruby user refers to it. It's a bit difficult to
explain, but you can review what matz said over the years - from the old
article "The Philosophy of Ruby" 
https://www.artima.com/articles/the-philosophy-of-ruby in 2003, but also
in other issue discussions. See the suggestions to create Hashes with a
definite / default / max-size. Either way it can change the way how people
write code or think about problems.

For instance, I actually do not recall matz using the word "default definee".
In the blog entry you linked to from 2009 or so, the author arbitrarily
reasoned that "klass" should be called "defined definee":

Specifically this part:





 it has to be, there can be no ambiguity about where methods are defined. This issue is about exposing it, so what is unclear? How to expose it? "Could be a Module class method or a global method (Kernel) or a keyword."

I'll consider opening a new one with a specific proposal around Module#nesting(n).



----------------------------------------
Feature #19682: ability to get a reference to the "default definee" 
https://bugs.ruby-lang.org/issues/19682#change-103285

* Author: bughit (bug hit)
* Status: Rejected
* Priority: Normal
----------------------------------------
https://blog.yugui.jp/entry/846

"default definee" is a pretty important context so why not make it easy to identify?

Could be a Module class method or a global method (Kernel) or a keyword.



-- 
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/

In This Thread