[ruby-core:109186] [Ruby master Misc#18836] DevMeeting-2022-07-21

Issue #18836 has been updated by jeremyevans0 (Jeremy Evans).


* [Bug #18770] Inconsistent behavior of IO/StringIO's each methods when called with nil as a separator, limit and chomp: true (jeremyevans0)
  * When using `nil` separator and `chomp` keyword, should IO chomp a final line separator?
  * I don't think it should, as `chomp` should only remove separators, and `nil` separator means no separator.
  * Assuming we should not chomp in this case, is the pull request acceptable?
* [Bug #18768] Inconsistent behavior of IO, StringIO and String each_line methods when return paragraph and chomp: true passed (jeremyevans0)
  * When using paragraph separator and `chomp`, should String#each_line be changed to chomp paragraphs instead of lines?
  * Assuming we should chomp paragraphs in this case, is the pull request acceptable?
* [Bug #18905] :"@=".inspect is non-evaluatable (jeremyevans0)
  * I don't think this is a bug, since Ruby does not attempt to ensure inspect returns valid Ruby code (e.g. `Object#inspect`).
  * Do we want to change it so that `Symbol#inspect` always returns valid ruby code (something you can pass to `eval`)?
* [Bug #18837] Not possible to evaluate expression with numbered parameters in it (jeremyevans0)
  * I agree with the poster that this isn't a bug, the issue should probably be switched to feature.
  * Do we want to change things so that bindings can deal with numbered parameters?
* [Bug #18784] `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions (jeremyevans0)
  * Should these methods only swallow exceptions if passed files that don't exist?

----------------------------------------
Misc #18836: DevMeeting-2022-07-21
https://bugs.ruby-lang.org/issues/18836#change-98327

* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting

**Date: 2022/07/21 13:00-17:00** (JST)
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 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 2022/07/18. 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/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>