From: "jeremyevans0 (Jeremy Evans) via ruby-core" Date: 2024-05-29T16:17:37+00:00 Subject: [ruby-core:118063] [Ruby master Misc#20435] DevMeeting-2024-06-06 Issue #20435 has been updated by 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 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. * [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. ---------------------------------------- Misc #20435: DevMeeting-2024-06-06 https://bugs.ruby-lang.org/issues/20435#change-108490 * Author: mame (Yusuke Endoh) * Status: Open ---------------------------------------- # 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-04-17.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](https://gist.github.com/mame/b0390509ce1491b43610b9ebb665eb86). 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. -- 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/