Ruby Issue Tracking System

07/25/2022

12:53 AM Ruby master Feature #18668: Merge `io-nonblock` gems into core

ianks (Ian Ker-Seymer) wrote in #note-21:
> IMO, we really do need to support this use case. Even if it were just fi... shyouhei (Shyouhei Urabe)

07/22/2022

12:10 PM Ruby master Bug #18780: Incorrect binding receiver for C API rb_eval_string()

Yes, it is a typo. Thank you. shyouhei (Shyouhei Urabe)

12:24 AM Ruby master Bug #18780: Incorrect binding receiver for C API rb_eval_string()

Updating the header document.
```patch
From b968f277386649b7531a8999be54eacf3c599cdb Mon Sep 17 00:00:00 2001
From: ... shyouhei (Shyouhei Urabe)

07/19/2022

12:40 AM Ruby master Misc #18921: Remove workaround for some fixed bug (llvm.4898 & 38095)?

Well I'm not against deleting those parts someday, but our CI still have clang-3.9 coverage. It seems we still need ... shyouhei (Shyouhei Urabe)

07/11/2022

07:24 AM Ruby master Bug #18893 (Closed): Don't redefine memcpy(3)

This is fixed and will be included in the next release. Thank you! shyouhei (Shyouhei Urabe)

07/07/2022

01:10 PM Ruby master Revision 7f64989e (git): do not define our own version of memcpy

The (sole) use of memcpy in our public header is now replaced to
directly call ruby_nonempty_memcpy, and the previous... shyouhei (Shyouhei Urabe)

07/06/2022

12:26 AM Ruby master Bug #18893: Don't redefine memcpy(3)

This is my take:
```patch
From 505d00311d82fdbed80688e9db792c3b54b8ee27 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E5... shyouhei (Shyouhei Urabe)

07/05/2022

01:00 AM Ruby master Bug #18893 (Open): Don't redefine memcpy(3)

alx (Alejandro Colomar) wrote in #note-2:
> Actually, ISO C specifies (indirectly) that `memcpy(dest, NULL, 0)` is U... shyouhei (Shyouhei Urabe)

07/04/2022

01:14 AM Ruby master Bug #18893 (Rejected): Don't redefine memcpy(3)

alx (Alejandro Colomar) wrote:
> ```
> alx@asus5775:/usr/include$ grepc memcpy
> ./string.h:43:
> extern void *me... shyouhei (Shyouhei Urabe)

06/29/2022

08:02 AM Ruby master Bug #18881: IO#read_nonblock raises IOError when called following buffered character IO

Basically yes. Some edge cases can be considered though (e.g. IO#flush could also reset this, IO#pread could be spec... shyouhei (Shyouhei Urabe)