ko1 (Koichi Sasada)
- Login: ko1
- Registered on: 05/28/2008
- Last sign in: 04/16/2025
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 85 | 600 | 685 |
Reported issues | 15 | 199 | 214 |
Projects
Project | Roles | Registered on |
---|---|---|
Ruby | Committer | 05/28/2008 |
Like
Activity
04/12/2025
-
01:13 AM Ruby Feature #21262: Proposal: `Ractor::Port`
- The important point is that we have limited "blocking" synchronization (introduced by cross-Ractor communication) to ...
-
01:10 AM Ruby Feature #21262: Proposal: `Ractor::Port`
- Now I understand that `find_work` takes a time and if no consumers are ready, we can't run `find_work` if there is no...
04/11/2025
-
06:14 PM Ruby Feature #21262: Proposal: `Ractor::Port`
- > The problem with the above code is that the consumer Ractor will starve until find_work returns.
I think it is s... -
09:37 AM Ruby Misc #21100: DevMeeting before RubyKaigi 2025
- I'd like to go through the discussion in the order written in this HackMD (with Matz's approval).
https://hackmd.i...
04/10/2025
-
02:55 PM Ruby Misc #21100: DevMeeting before RubyKaigi 2025
- * [Feature #21262] Proposal: `Ractor::Port` (ko1)
* Considering with [`Channel`](https://bugs.ruby-lang.org/issues... -
02:43 PM Ruby Feature #21262 (Assigned): Proposal: `Ractor::Port`
- # Proposal: `Ractor::Port`
In concurrent Ruby applications using Ractors, safely and efficiently communicating res...
04/08/2025
-
12:45 AM Ruby Feature #21254: Inlining Class#new
- `swap` is remained?
03/13/2025
-
09:49 AM Ruby Feature #21042: Add and expose Thread#memory_allocations memory allocation counters
- Matz said he is positive on this proposal.
I have some considerations.
* Now current proposal doesn't increase ...
03/11/2025
-
03:16 PM Ruby Bug #21171: Segfault on large stack (RUBY_THREAD_VM_STACK_SIZE) on 3.4.2
- I could repro on ruby_3_4 edge but not sure why.
With
```diff
diff --git a/include/ruby/assert.h b/include/ru... -
07:56 AM Ruby Bug #21146: VM_ASSERT(expr) gives bad bug report results when another ractor fails an assertion during printing of report
- Your patch uses `RB_VM_LOCK_ENTER_NO_BARRIER` but it should block normal use of `rb_bug()` (using `rb_bug()` is irreg...
Also available in: Atom