[#105450] [Ruby master Feature#18228] Add a `timeout` option to `IO.copy_stream` — "byroot (Jean Boussier)" <noreply@...>
Issue #18228 has been reported by byroot (Jean Boussier).
11 messages
2021/09/27
[ruby-core:105436] [Ruby master Misc#18174] DevelopersMeeting20211021Japan
From:
"ioquatix (Samuel Williams)" <noreply@...>
Date:
2021-09-27 04:04:36 UTC
List:
ruby-core #105436
Issue #18174 has been updated by ioquatix (Samuel Williams).
- [Feature #18035] Introduce general model/semantic for immutable by default.
- Can we agree on interface and implementation.
- `Process::Status` is example use-case. Should be many more.
- [Feature #18083] Capture error in ensure block.
- Can we deprecate `$!` (& `$@`)? It's dangerous and every use case is better with explicit capture. Also may have some performance advantages.
- [Feature #18020] Introduce `IO::Buffer` for fiber scheduler.
- For efficient file IO we need an internal buffer with well defined semantics suitable for IO.
- [Feature #17369] Introduce non-blocking `Process.wait`, `Kernel.system` and related methods.
- Currently, `$?` is thread-local, but it should be fiber local.
- Should we try to fix `$?` or deprecate it?
- Introduce new interface? `system(...) {|status| ...}`?
----------------------------------------
Misc #18174: DevelopersMeeting20211021Japan
https://bugs.ruby-lang.org/issues/18174#change-93883
* Author: mame (Yusuke Endoh)
* Status: Open
* Priority: Normal
----------------------------------------
# The next dev meeting
**Date: 2021/10/21 13:00-17:00**
Place/Sign-up/Agenda/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 log about the discussion to a 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 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 2021/10/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:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>