[ruby-core:113081] [Ruby master Misc#19525] DevMeeting-2023-04-13

Issue #19525 has been updated by byroot (Jean Boussier).


* [Feature #19561] ObjectSpace::WeakMap#delete and ObjectSpace::WeakKeyMap#delete (byroot)
  * When used as a weak set, it can be convenient to eagerly delete some keys.
* [Feature #19538] Performance warnings (byroot and eregon)
  * Disabled by default, enabled with `-W:performance`.
  * Would allow the VM or YJIT to indicate when it has to deoptimize because of some construct.
  * For example: transitioning to `SHAPE_TOO_COMPLEX`, mega-morphic call sites, etc.
* [Feature #19528] `JSON.load` enabling `create_additions: true` by default is surprising and lead to security vulnerabilities (byroot)
  * `JSON.load` is the natural method to reach to as "load/dump" is the standard Ruby interface (`Marshal.load`, `YAML.load`, etc).
  * Various linters have to ben `load` and recommend to use `parse` instead.
  * I think json 2.x should warn when this feature is implicitly enabled, and json 3.x should disable it by default.
  * This has led to multiple CVE in the past.
* [Feature #19560] `IO#close_on_fork=` and `IO#close_on_fork?` (byroot)
  * `O_CLOFORK` was added to the POSIX spec in 2020, and some system (not Linux) supports it.
  * Ruby could emulate it.
  * Such feature would make it much easier to write fork-safe network clients.


----------------------------------------
Misc #19525: DevMeeting-2023-04-13
https://bugs.ruby-lang.org/issues/19525#change-102616

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

**Date: 2023/04/13 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 2023/04/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 -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/