From: eregontp@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95781] [Ruby master Misc#16333] DevelopersMeeting20191112Online to confirm Ruby 2.7 spec
Date: Sun, 10 Nov 2019 22:44:32 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-82605.20191110224432.019ad420ce379d87@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16333.20191107214310@ruby-lang.org
Issue #16333 has been updated by Eregon (Benoit Daloze).
I'd be interested to attend but I think those hours will be too early for me (5-9 AM CET).
I think we should discuss and decide how to handle delegation in Ruby 2.7, Ruby 3 and later.
I wrote a blog post explaining the various possibilities and expressing my opinion about it, also asking feedback from the community:
https://eregon.me/blog/2019/11/10/the-delegation-challenge-of-ruby27.html
----------------------------------------
Misc #16333: DevelopersMeeting20191112Online to confirm Ruby 2.7 spec
https://bugs.ruby-lang.org/issues/16333#change-82605
* Author: ko1 (Koichi Sasada)
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Hi, we will open DevMeeting with Matz.
Date: 2019/11/12 13:00-17:00
Place: online meeting (ask me if you want to attend. I'll share it on ruby-comitter's slack #devmeeting)
Topics: confirm Ruby 2.7 specs with Matz
Please write your new features in NEWS file and we will read them.
If you have special topics you want to discuss, please tell comment them.
Thanks,
Koichi
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-11-10 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16333.20191107214310@ruby-lang.org>
2019-11-07 21:43 ` [ruby-core:95751] [Ruby master Misc#16333] DevelopersMeeting20191112Online to confirm Ruby 2.7 spec ko1
2019-11-10 13:03 ` [ruby-core:95776] " shevegen
2019-11-10 22:44 ` eregontp [this message]
2019-11-19 8:03 ` [ruby-core:95885] " ko1
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-82605.20191110224432.019ad420ce379d87@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).