[ruby-core:120215] [Ruby master Misc#20949] DevMeeting-2025-01-09

[ruby-core:120215] [Ruby master Misc#20949] DevMeeting-2025-01-09

[mame (Yusuke Endoh) via ruby-core]

Issue #20949 has been reported by mame (Yusuke Endoh).

----------------------------------------
Misc #20949: DevMeeting-2025-01-09
https://bugs.ruby-lang.org/issues/20949

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

**Date: 2025/01/09 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 2025/01/06. 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/

[ruby-core:120484] [Ruby master Misc#20949] DevMeeting-2025-01-09

[byroot (Jean Boussier) via ruby-core]

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


* [Feature #20993] Allow `class <constant-path> = <expression>` syntax (byroot)
  * Useful for defining `Struct` and `Data` subclasses. See [Bug #20943]
  * It's just sugar for `<constant-path> = <expression>; class <constant-path>`
  * Would be allowed for `module` as well.
* [Feature #20878] A new C API to create a String by adopting a pointer (byroot)
  * Following the last discussion I think the API could receive a pointer to the `free` function to use.
  * e.g. `str = rb_enc_str_adopt(buf->ptr, buf->len, buf->capa, rb_utf8_encoding(), free);`
  * This allow the API to fallback to a copy if the free function isn't compatible with `ruby_xfree`

----------------------------------------
Misc #20949: DevMeeting-2025-01-09
https://bugs.ruby-lang.org/issues/20949#change-111268

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

**Date: 2025/01/09 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 2025/01/06. 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/

[ruby-core:120505] [Ruby master Misc#20949] DevMeeting-2025-01-09

[Eregon (Benoit Daloze) via ruby-core]

Issue #20949 has been updated by Eregon (Benoit Daloze).


* [Feature #21005] Update the source location method to include line start/stop and column start/stop details (eregon)
  * How about adding end line and start/end columns to `#source_location`? It seems straightforward and compatible.
  * How about a new `#code_location` method returning an object with line/column/offset info and also a convenient method to return the source code snippet of that location? See https://bugs.ruby-lang.org/issues/21005#note-3

----------------------------------------
Misc #20949: DevMeeting-2025-01-09
https://bugs.ruby-lang.org/issues/20949#change-111298

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

**Date: 2025/01/09 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 2025/01/06. 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/

[ruby-core:120560] [Ruby master Misc#20949] DevMeeting-2025-01-09

[sampersand2 (Sam Westerman) via ruby-core]

Issue #20949 has been updated by sampersand2 (Sam Westerman).


* [Feature #21015] Add in a `-g` flag, like `-s` but with a few more quality of life features (sampersand2)
  * There's a hole in ruby for very simple argument processing to very short scripts (<=10 lines.)
  * The `-s` flag somewhat fills this, but most egregiously doesn't let you chain shortform options (`-abc` != `-a -b -c`).
  * I've gotten positive sentiment from quite a few people on the Ruby discord about this, so I think it's worth discussing

----------------------------------------
Misc #20949: DevMeeting-2025-01-09
https://bugs.ruby-lang.org/issues/20949#change-111371

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

**Date: 2025/01/09 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 2025/01/06. 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/