General

Profile

chancancode (Godfrey Chan)

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 3 3

Activity

02/13/2026

09:30 PM Ruby Revision 93e68cac (git): ZJIT: unify `hir::Insn::{Send,SendWithoutBlock}` (GH-16143)
After GH-15911, we largely apply the same treatment to these two
variants everywhere. In `type_specialize`, there are two ~100 LOC
match arms that shared 90% of the code. Unifying these allowed the
code to be shared more easily.
---
**...
chancancode (Godfrey Chan)

01/28/2026

09:32 PM Ruby Revision 2d5460e4 (git): ZJIT: Optimize send-with-block to iseq methods (#15911)
~~Two commits:~~
### zjit: Optimize send-with-block to iseq methods
This commit enables JIT-to-JIT calls for send instructions with literal blocks (e.g., `foo { |x| x * 2 }`), rather than falling back to the `rb_vm_send` C wrapper. Thi...
chancancode (Godfrey Chan)

12/25/2025

12:06 AM Ruby Revision 3c4cda10 (git): [DOC] Add back Rust 1.85.0 requirement to NEWS.md (#15728)
* [DOC] Add back Rust 1.85.0 requirement to NEWS.md
Addresses k0kubun's review in https://github.com/ruby/ruby/pull/15711#issuecomment-3690541074
NEWS.md serves both CRuby developers as well as end-users. As the
release date closes in,...
chancancode (Godfrey Chan)

12/24/2025

06:43 AM Ruby Revision 88d6c5aa (git): [DOC] Update ZJIT status in NEWS.md
As for Ruby v4.0.0-preview3, ZJIT support is enabled by default on
supported platforms. The previous phrasing is not relevant for most
users. Replaced with brief instructions for enabling the JIT itself.
chancancode (Godfrey Chan)

11/18/2025

04:35 PM Ruby Revision f84bbb42 (git): ZJIT: add support for lazy `RubyVM::ZJIT.enable`
This implements Shopify#854:
- Splits boot-time and enable-time initialization,
tracks progress with `InitializationState` enum
- Introduces `RubyVM::ZJIT.enable` Ruby method for
enabling the JIT lazily, if not already enabled
- I...
chancancode (Godfrey Chan)

11/27/2015

04:35 PM Ruby Bug #11744: Open files being GC'ed while still in use
Actually, @nurse you are right!
It turns out that rb-inotify uses `IO.fd_for` in its code. At some point, the system starts recycling FD numbers, so we got the same FD number on our file as the rb-inotify object waiting to be GC'ed. W...
chancancode (Godfrey Chan)
09:22 AM Ruby Bug #11744: Open files being GC'ed while still in use
> We have found the issue
Looks like I spoke too soon! The issue is back with listen 3.0.5.
> ...
I don't *think* that's the case here, but I could be completely wrong.
In the [simplified reproduction script](https://github.com/...
chancancode (Godfrey Chan)

11/26/2015

06:25 PM Ruby Bug #11744: Open files being GC'ed while still in use
We have found the issue – apparently, listen 3.0.4 and below [doesn't actually teardown the inotify watchers](https://github.com/guard/listen/issues/353). Upgrading to 3.0.5 (which implemented the teardown) fixes the issue for us.
How...
chancancode (Godfrey Chan)
06:12 PM Ruby Bug #11744 (Closed): Open files being GC'ed while still in use
Hello!
We recently added a feature on Rails that uses the [`listen` gem](https://github.com/guard/listen) under-the-hood. Since we enabled those tests, we have been seeing random failures on Travis CI like [these](https://travis-ci.or...
chancancode (Godfrey Chan)

08/27/2015

09:10 PM Ruby Bug #11490: Allocation tracer sometimes attributes allocations to the wrong source file/line
Thinking about it more, it seems my original hunch is *probably* correct: when loading/parsing/evaluating the file, the VM has to allocate a large amount of objects (e.g. when it runs `def zomg; ...; end`, it needs to create the "immorta... chancancode (Godfrey Chan)

Also available in: Atom