[#113756] [Ruby master Bug#19711] NoMethodError "private method `new' called for class" since bebd05fb51ea65bc57344b67100748200f8311eb — "yahonda (Yasuo Honda) via ruby-core" <ruby-core@...>

Issue #19711 has been reported by yahonda (Yasuo Honda).

7 messages 2023/06/05

[#113771] [Ruby master Feature#19712] IO#reopen removes singleton class — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19712 has been reported by itarato (Peter Arato).

11 messages 2023/06/05

[#113782] [Ruby master Bug#19716] SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc) — "alexdowad (Alex Dowad) via ruby-core" <ruby-core@...>

Issue #19716 has been reported by alexdowad (Alex Dowad).

6 messages 2023/06/07

[#113788] [Ruby master Bug#19717] `ConditionVariable#signal` is not fair when the wakeup is consistently spurious. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19717 has been reported by ioquatix (Samuel Williams).

13 messages 2023/06/07

[#113819] [Ruby master Feature#19720] Warning for non-linear Regexps — "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>

Issue #19720 has been reported by Eregon (Benoit Daloze).

11 messages 2023/06/08

[#113835] [Ruby master Misc#19722] DevMeeting-2023-07-13 — "mame (Yusuke Endoh) via ruby-core" <ruby-core@...>

Issue #19722 has been reported by mame (Yusuke Endoh).

9 messages 2023/06/09

[#113944] [Ruby master Feature#19737] Add `IO::Buffer#cat` for concat `IO::Buffer` instances — "unasuke (Yusuke Nakamura) via ruby-core" <ruby-core@...>

Issue #19737 has been reported by unasuke (Yusuke Nakamura).

7 messages 2023/06/19

[#113953] [Ruby master Bug#19739] Key cannot be found in a Hash when slice! method is applied to the key — "ilya.andreyuk (Ilya Andreyuk) via ruby-core" <ruby-core@...>

Issue #19739 has been reported by ilya.andreyuk (Ilya Andreyuk).

9 messages 2023/06/20

[#113966] [Ruby master Bug#19742] Introduce `Module#anonymous?` — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19742 has been reported by ioquatix (Samuel Williams).

47 messages 2023/06/21

[#114025] [Ruby master Feature#19744] Namespace on read — "tagomoris (Satoshi TAGOMORI) via ruby-core" <ruby-core@...>

Issue #19744 has been reported by tagomoris (Satoshi TAGOMORI).

71 messages 2023/06/27

[#114032] [Ruby master Misc#19747] Propose Kevin Newton and Jemma Issroff as core committers — "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>

Issue #19747 has been reported by k0kubun (Takashi Kokubun).

8 messages 2023/06/28

[#114038] [Ruby master Bug#19749] Confirm correct behaviour when attaching private method with `#define_method` — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19749 has been reported by itarato (Peter Arato).

15 messages 2023/06/28

[ruby-core:113995] [Ruby master Feature#19742] Introduce `Module#anonymous?`

From: janosch-x via ruby-core <ruby-core@...>
Date: 2023-06-22 07:09:39 UTC
List: ruby-core #113995
Issue #19742 has been updated by janosch-x (Janosch M=FCller).





fxn (Xavier Noria) wrote in #note-17:

> def self.name [...] I think overriding such a core method for an attribut=
e that is out of reach, managed internally by Ruby, is questionable [...] C=
an people override `Array#size` to return 7? Yes, they can.



The problem with `name` is that it is a common, uh, name. It is also not as=
 obvious that it is a part of the core as with `Array#size`.



Coincidental overrides like [these](https://github.com/search?q=3Drepo%3Afa=
ker-ruby%2Ffaker%20name&type=3Dcode) are probably somewhat common.







----------------------------------------

Feature #19742: Introduce `Module#anonymous?`

https://bugs.ruby-lang.org/issues/19742#change-103653



* Author: ioquatix (Samuel Williams)

* Status: Open

* Priority: Normal

----------------------------------------

As a follow-on <from https://bugs.ruby-lang.org/issues/19521>, I'd like pro=
pose we introduce `Module#anonymous?`.



In some situations, like logging/formatting, serialisation/deserialization,=
 debugging or meta-programming, we might like to know if a class is a prope=
r constant or not.



However, this brings about some other issues which might need to be discuss=
ed.



After assigning a constant, then removing it, the internal state of Ruby st=
ill believes that the class name is permanent, even thought it's no longer =
true.



e.g.



```

m =3D Module.new

m.anonymous? # true



M =3D m

m.anonyomous # false



Object.send(:remove_const, :M)

M # uninitialized constant M (NameError)



m.anonymous? # false

```



Because RCLASS data structure is not updated after the constant is removed,=
 internally the state still has a "permanent class name".



I want to use this proposal to discuss this issue and whether there is anyt=
hing we should do about such behaviour (or even if it's desirable).



Proposed PR: https://github.com/ruby/ruby/pull/7966



cc @fxn







--=20

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-c=
ore.ml.ruby-lang.org/

In This Thread