[ruby-core:107506] [Ruby master Misc#18557] DevMeeting-2022-02-17

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


* [Bug #18487] Kernel#binding behaves differently depending on implementation language of items on the stack (jeremyevans0)
  * Is it OK to limit Kernel#binding to only look at the preceding frame, instead of the closest Ruby-level frame?
  * If so, is the patch acceptable?
* [Bug #16663] Add block or filtered forms of Kernel#caller to allow early bail-out (jeremyevans0)
  * Since the last developer meeting, a prototype has been created.
  * Is the behavior of the prototype acceptable?
  * Incorrect usage with `to_enum` raises `StopIteration` instead of crashing.  Is that acceptable?
* [Bug #14103] Regexp absense operator has no chance to `^C` (jeremyevans0)
  * One possible way around this is checking for interrupts and potentially yield to another thread every N times during backtracking.
  * I submitted a pull request to do that (N = 1000), and it fixes the example given.
  * Is such an approach acceptable? If so, is the patch acceptable?
  * One issue not addressed by the patch is the modification of the string being searched by another thread during regexp evaluation (potentially causing a crash), but I'm not sure whether that is possible.

----------------------------------------
Misc #18557: DevMeeting-2022-02-17
https://bugs.ruby-lang.org/issues/18557#change-96411

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

**Date: 2022/02/17 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/02/14. 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>