From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:103193] [Ruby master Misc#17734] DevelopersMeeting20210416Japan
Date: Fri, 02 Apr 2021 22:13:34 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-91269.20210402221333.18@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17734.20210320025151.18@ruby-lang.org
Issue #17734 has been updated by jeremyevans0 (Jeremy Evans).
* [Bug #17398] SyntaxError in endless method (jeremyevans0)
* I don't believe this is a bug, but maybe it is a useful feature.
* @mame has a patch that allows commands as the RHS of a endless method.
* However, @mame's patch doesn't allow direct usage with method visibility methods such as private.
* Do we want to support this syntax, or can this be closed (or moved to Feature)?
* [Bug #17403] Remove Fixnum and Bignum (jeremyevans0)
* Do we want to remove Fixnum and Bignum in Ruby 3.1?
* If not, can we decide on a later version where they can be removed, such as 3.2 or 4.0?
* [Bug #16983] RubyVM::AbstractSyntaxTree.of(method) returns meaningless node if the method is defined in eval (jeremyevans0)
* `RubyVM::AbstractSyntaxTree.of(method)` relies on reading the file with the method source, which could have changed or could not exist at all.
* I don't think we can work around that without keeping the abstract syntax tree or source code of all methods in memory, which seems wasteful.
* Is the current behavior a bug, or should we just accept the current behavior as spec and close this?
* [Bug #9542] Delegator does not delegate protected methods (jeremyevans0)
* Do we want to add a way to tell if a method was called with an implicit receiver or self?
* We may be able to implement this via a VM frame flag and a method to check it.
* If we don't want to add such a way, can we accept the current behavior as spec and close this?
* [Bug #11230] Should rb_struct_s_members() be public API? (jeremyevans0)
* This is still public in the C-API.
* Do we want to keep it and close this issue, or do we want to remove it?
* If we want to remove it, how should it be deprecated?
----------------------------------------
Misc #17734: DevelopersMeeting20210416Japan
https://bugs.ruby-lang.org/issues/17734#change-91269
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/04/16 13:00-17:00**
Place/Sign-up/Agenda/Log: *TBD*
- 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 log about the discussion to a 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 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 2021/04/13. 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/
next prev parent reply other threads:[~2021-04-02 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 2:51 [ruby-core:102934] [Ruby master Misc#17734] DevelopersMeeting20210416Japan mame
2021-04-02 22:13 ` merch-redmine [this message]
2021-04-02 23:57 ` [ruby-core:103194] " tenderlove
2021-04-07 6:33 ` [ruby-core:103265] " mame
2021-04-07 16:24 ` [ruby-core:103270] " daniel
2021-04-08 12:35 ` [ruby-core:103302] " marcandre-ruby-core
2021-04-08 13:05 ` [ruby-core:103304] " jean.boussier
2021-04-13 15:08 ` [ruby-core:103430] " finch.parker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-91269.20210402221333.18@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).