ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: XrXr@users.noreply.github.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95848] [Ruby master Misc#16262] DevelopersMeeting20191128Japan
Date: Thu, 14 Nov 2019 03:46:40 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-82681.20191114034640.ad4e00b72bef7602@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16262.20191018120331@ruby-lang.org

Issue #16262 has been updated by alanwu (Alan Wu).


- [Bug #15620] Block argument usage affects lambda semantic
  - I find the current behaviour unreasonably confusing and would like to see improvement, even though the bug doesn't really show up in the real world often.
  - I have a [pull request](https://github.com/ruby/ruby/pull/2289) which restores the behaviour found in Ruby 2.4.x and warns about it, based off of matz's comment in [[ruby-core:94054]](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/94054).
  - Could someone confirm that is the desired fix? If it is the fix we want, could someone review the PR?


----------------------------------------
Misc #16262: DevelopersMeeting20191128Japan
https://bugs.ruby-lang.org/issues/16262#change-82681

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
Please comment on your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary.
(your summary/comment will help us because we don't need to read all of the ticket comments)

*DO NOT* discuss then on this ticket, please.

----
Date: 2019/11/28 13:00-17:00
Place, Sign-up, and Log: https://docs.google.com/document/d/1AZ74HXEedKksJwhEUPIlnRxAUgchndZPZYAKjGPMsFI/edit#

# NOTES

- 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.

# Agenda

## Next dev-meeting

## About 2.7 timeframe

## Check security tickets

## Discussion

----

Please comment on your favorite ticket we need to discuss with *the following format*.

```
* [Ticket ref] Ticket title (your name)
* your comment why you want to put this ticket here if you want to add.
```

Your comment is very important if you are no attendee because we can not ask why you want to discuss it.

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.
```

We don't guarantee to put tickets in the agenda if the comment violates the format (because it is hard to copy&paste).

**A short summary of a ticket is strongly recommended. We cannot read all discussion of the ticket in a limited time.**
A proposal is often changed during the discussion, so it is very helpful to summarize the latest/current proposal, post it as a comment in the ticket, and write a link to the comment. 




-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2019-11-14  3:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-16262.20191018120331@ruby-lang.org>
2019-10-18 12:03 ` [ruby-core:95420] [Ruby master Misc#16262] DevelopersMeeting20191128Japan mame
2019-10-18 12:08 ` [ruby-core:95421] " mame
2019-10-18 16:12 ` [ruby-core:95423] " merch-redmine
2019-10-22 22:58 ` [ruby-core:95484] " duerst
2019-10-26 12:42 ` [ruby-core:95564] " zverok.offline
2019-11-04 21:13 ` [ruby-core:95678] " jonathan
2019-11-05 12:20 ` [ruby-core:95697] " manga.osyo
2019-11-10 14:00 ` [ruby-core:95777] " lourens
2019-11-14  3:46 ` XrXr [this message]
2019-11-24  2:25 ` [ruby-core:95919] " mame
2019-11-24  3:14 ` [ruby-core:95921] " mail
2019-11-24  9:19 ` [ruby-core:95922] " kazuki
2019-11-24 22:46 ` [ruby-core:95929] " eregontp
2019-11-24 23:14 ` [ruby-core:95932] " mame
2019-11-25  6:00 ` [ruby-core:95938] " sawadatsuyoshi
2019-11-27  1:06 ` [ruby-core:95969] " lourens
2019-11-27 11:58 ` [ruby-core:95979] " hsbt
2019-11-27 12:49 ` [ruby-core:95980] " zverok.offline
2019-11-28  6:40 ` [ruby-core:96013] " jean.boussier
2019-11-28 10:15 ` [ruby-core:96019] " eregontp
2019-11-30  4:06 ` [ruby-core:96033] " mame

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-82681.20191114034640.ad4e00b72bef7602@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).