From: "shugo (Shugo Maeda) via ruby-core" <ruby-core@...>
Date: 2026-10-02T02:28:36+00:00
Subject: [ruby-core:126907] [Ruby Misc#22394] DevMeeting-2026-10-07

Issue #22394 has been updated by shugo (Shugo Maeda).


* [Feature #22392] Allow refinements to define && and || (shugo)
  * I propose to allow `&&` and `||` to be defined in refinements, so that DSLs can write `where { name == "x" && age > 20 }` instead of `where { (name == "x") & (age > 20) }`.
  * The right-hand side is evaluated before the hook is called, so a hook never short-circuits; code outside `using` or `Proc#refined` keeps the current behavior, and defining them outside refinements raises NameError.
  * `&&=` and `||=`, conditions such as `if a && b`, and statements that discard the value keep the current behavior.
  * PoC: https://github.com/ruby/ruby/pull/19133
  * Objections on the ticket: the cost for non-users (alanwu) and that `&`/`|` with parentheses is readable enough (matheusrich). With conditions excluded, code that doesn't use the hooks pays +2..3 instructions per `&&`/`||` whose value is used and about +0.4% of iseq memory. Is the feature worth that?


----------------------------------------
Misc #22394: DevMeeting-2026-10-07
https://bugs.ruby-lang.org/issues/22394#change-119290

* Author: hsbt (Hiroshi SHIBATA)
* Status: Open
----------------------------------------
# The next dev meeting

**Date: 2026/10/07 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 2026/10/04. 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 -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/