Misc #20435: DevMeeting-2024-06-06

• Status: Closed
• Assignee: -

[mame (Yusuke Endoh)]

The next dev meeting

Date: 2024/06/06 13:00-17:00 (JST)
Log: https://github.com/ruby/dev-meeting-log/blob/master/2024/DevMeeting-2024-06-06.md

• Dev meeting IS NOT a decision-making place. All decisions should be done at the bug tracker.
• Dev meeting is a place we can ask Matz, nobu, nurse and other developers directly.
• Matz is a very busy person. Take this opportunity to ask him. If you can not attend, other attendees can ask instead of you (if attendees can understand your issue).
• We will write a record of the discussion in the file or to each ticket in English.
• All activities are best-effort (keep in mind that most of us are volunteer developers).
• The date, time and place of the meeting are scheduled according to when/where we can reserve Matz's time.
• DO NOT discuss then on this ticket, please.

Call for agenda items

If you have a ticket that you want matz and committers to discuss, please post it into this ticket in the following format:

* [Ticket ref] Ticket title (your name)
  * Comment (A summary of the ticket, why you put this ticket here, what point should be discussed, etc.)

Example:

* [Feature #14609] `Kernel#p` without args shows the receiver (ko1)
  * I feel this feature is very useful and some people say :+1: so let discuss this feature.

• It is recommended to add a comment by 2024/06/10. We hold a preparatory meeting to create an agenda a few days before the dev-meeting.
• The format is strict. We'll use this script to automatically create an markdown-style agenda. We may ignore a comment that does not follow the format.
• Your comment is mandatory. We cannot read all discussion of the ticket in a limited time. We appreciate it if you could write a short summary and update from a previous discussion.

[mame (Yusuke Endoh)]

• Related to Misc #14770: [META] DevelopersMeeting added

[mame (Yusuke Endoh)]

Note: The next dev meeting in May will be held in person, co-located with RubyKaigi 2024 in Okinawa, Japan. @ko1 (Koichi Sasada) will create the ticket for that separately.

[mame (Yusuke Endoh)]

• Description updated (diff)

[hsbt (Hiroshi SHIBATA)]

• Subject changed from DevMeeting-2024-06-13 to DevMeeting-2024-06-06
• Description updated (diff)

Meeting date is updated with Matz's schedule: 6/13 to 6/6

[kddnewton (Kevin Newton)]

• [Bug #20504] Interpolated string literal in regexp encoding handling (kddnewton)
  • I think there is an inconsistency here that we can solve by using the same codepath for creating regexps.
  • Could we change this? It should be minimal impact.
• [Bug #20478] Circular parameter syntax error rules (kddnewton)
  • I think there is an inconsistency here, impacted by the presence of pipes.
  • Could we change this to be consistent? Either all reads at depth 0 or all reads at any depth.
• [Misc #20488] Document source file size restrictions (kddnewton)
  • Could we restrict source files to 32-bits?
  • It would help on memory size for parsers.

[mame (Yusuke Endoh)]

• [Bug #20314] Simultaneous Timeout expires may raise an exception after the block (mame)
  • I need a wisdom from committers on how to fix nested timeouts.

[jeremyevans0 (Jeremy Evans)]

• [Bug #20433] Hash.inspect for some hash returns syntax invalid representation (jeremyevans0)
  • Some symbols when used as hash keys results in Hash#inspect returning invalid syntax.
  • Most compatible fix is only using spaces around => when necessary.
  • Most consistent fix would be always using spaces around =>.
  • Alternative fix would be to have Symbol#inspect quote the symbols, even though quotes aren't required outside of usage as a hash key.
  • Which approach should be used?
• [Bug #20043] defined? checks for method existence but only sometimes (jeremyevans0)
  • I have a pull request to fix this (needs an update for prism).
  • However, @ko1 (Koichi Sasada) mentioned we may want to deprecate defined? when used with expressions.
  • Do we want to deprecate such usage of defined??
• [Bug #19749] Confirm correct behaviour when attaching private method with #define_method (jeremyevans0)
  • I think the behavior of not changing method visibility is definitely a bug.
  • Last reviewed at the August 2023 developer meeting, still waiting on a decision from @matz (Yukihiro Matsumoto).
• [Bug #18622] const_get still looks in Object, while lexical constant lookup no longer does (jeremyevans0)
  • It would be nice to have consistent behavior.
  • Last reviewed at the June 2023 developer meeting, still waiting on a decision from @matz (Yukihiro Matsumoto).

[bughit (bug hit)]

• [Bug #20513] the feature of kwargs in index assignment has been removed without due consideration of utility, compatibility, consistency and logic (bughit)
  • it doesn't make sense to remove a feature because there are fixable edge-case bugs in its implementation
  • it doesn't make sense from a higher level language design perspective to allow kwargs in index but not in index assignment
  • instead of removal, index assignment should get proper/real kwargs and the multiple assignment problem should be fixed

[byroot (Jean Boussier)]

• [Feature #19998] Emit deprecation warnings when the old (non-Typed) Data_XXX API is used (byroot)
  • Marked as deprecated in the documentation as of Ruby 2.3.0 (2015)
  • Yet I found gems using it without realizing TypedData is preferred.
  • Proposed patch emit a deprecation warning when the gem is compiled: https://github.com/ruby/ruby/pull/10872

[akr (Akira Tanaka)]

• [Bug #20518] Escaped-newline in %W (akr)
  • I think it is a bug but fixing it causes (hopefully small) incompatibility.

[andrykonchin (Andrew Konchin)]

• [Misc #20407] Question about applying encoding modifier to an interpolated Regexp (andrykonchin)
  • The documentation states that a Regexp with only US-ASCII characters has US-ASCII encoding, otherwise a regular expression is assumed to use the source encoding. This can be overridden with encoding modifiers.
  • It isn't clear enough how a Regexp encoding (that Regexp#encoding method returns) is calculated in case an encoding modifier (e.g. u, e, etc) is specified for a Regexp with interpolation (e.g. /a #{ "b".encode("windows-1251") } c/e).
  • The encoding modifier is applied in some cases and isn't in other ones what seems confusing at first glance.
  • It seems result depends on a source encoding, characters of the Regexp literal fragments and encoding of Regexp interpolated fragments as well.
• [Bug #20416] IO#read doesn't preserve buffer encoding if maxlen = nil (andrykonchin)
  • IO#read and similar methods when called with buffer argument preserve its encoding.
  • But IO#read doesn't do so in case the maxlen argument is nil.
• [Bug #20319] Singleton class is being frozen lazily in some cases (andrykonchin)
  • When an object becomes frozen (with #freeze method call) only its own singleton class becomes frozen immediately.
  • Classes in the singleton classes chain become frozen only when they are returned to user with #singleton_class method call.
  • The object's singleton class' singleton class (and so on) doesn't become frozen even if it was already instantiated
  • This lazy freezing can be observed by a user when he gets a singleton class of the object's singleton class before freezing the object. After freezing the object the instantiated singleton class is still not frozen.
  • There might be several options (1) don't change anything, 2) freeze all the instantiated singleton classes in a chain immediately or 3) don't freeze singleton classes in a chain at all and stop freezing even an object's singleton class) and there is a PR with fix (https://github.com/ruby/ruby/pull/10245) but it's unclear what option is the best one.

[Eregon (Benoit Daloze)]

• [Feature #6648] Provide a standard API for retrieving all command-line flags passed to Ruby (eregon)
  • @nobu (Nobuyoshi Nakada) are you OK with RbConfig.ruby_args? If not can you suggest a better place?

[eightbitraptor (Matthew Valentine-House)]

• [Feature #20443] Allow Major GC's to be disabled
  • @ko1 (Koichi Sasada) is against the name disable_major
  • I would like advice from committers about what an appropriate name for this method should be.

[mame (Yusuke Endoh)]

• Description updated (diff)

[mame (Yusuke Endoh)]

• Status changed from Open to Closed