Ruby Issue Tracking System

12/03/2022

07:33 AM Ruby Feature #18980: `it` as a default block parameter

Ruby takes so much syntax last years. I fear it. Let's not strain our lovely language, please. funny_falcon (Yura Sokolov)

07/21/2018

08:09 AM Ruby Feature #14859: [PATCH] implement Timeout in VM

normalperson (Eric Wong) wrote:
> Yes. The "timeout scheduler" is the same idea I used for auto-fiber.
> ...
Still wonder, why you don't use binary min-heap for timers - most commonly used datastructure for this task.
It has guaran... funny_falcon (Yura Sokolov)

07/13/2018

04:58 AM Ruby Bug #14891: Pathname#join has different behaviour to File.join

I'd rather say that File.join is currently broken, and it should behave like Pathname.join. But probably I'm missing something. funny_falcon (Yura Sokolov)

04:52 AM Ruby Bug #14909: Method call with object that has to_hash method crashes (method with splat and keyword arguments)

Why your object has `to_hash` method?
Ruby uses long named methods for implicit conversion: `to_str` - if your object should act as a string, `to_int` - if your object should act as an integer, `to_ary` - if your object should act as ... funny_falcon (Yura Sokolov)

07/08/2018

09:46 AM Ruby Bug #14900: Extra allocation in String#byteslice

@ioquatix, your patch doesn't seems to be correct for me on first glance.
Imagine pipelined RPC server:
- we read data into buffer
- while buffer larger than request size
- detect first request and split buffer into request and r... funny_falcon (Yura Sokolov)

07/06/2018

06:10 PM Ruby Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

> Yes, they are great, but it's probably impossible to implement in Ruby.
It is impossible to implement Thread migration between native threads. All other is possible.
> ...
Don't get me wrong: most of code is linear and thread-saf... funny_falcon (Yura Sokolov)

07:48 AM Ruby Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

> In my experience, threads simply don't scale as as well as fibers, there is too much overhead.
Native threads doesn't scale.
But we have example of Go: goroutine is a really green thread, and they do really scale.
And Ruby 1.8 ha... funny_falcon (Yura Sokolov)

07/05/2018

06:12 PM Ruby Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

> It's also going to be more useful for existing code bases like ActionCable, Puma, Async, etc which use their own IO scheduler.
They have their own IO scheduler because ruby had just native threads, which are bad as IO scheduler.
Ok... funny_falcon (Yura Sokolov)

08:43 AM Ruby Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

@ioquatix About "extendable api" vs "implicit behavior" (ie between your proposal
for "Thread.scheduler=' and replacing "Thread" with green implementation),
I'd prefer "implicit behavior".
Because, there were already EM::Synchrony, th... funny_falcon (Yura Sokolov)

08:33 AM Ruby Feature #14736: Thread selector for flexible cooperative fiber based concurrency

I've shown `to_enum(:aga).to_a` to present the place where I wasn't right.
But if you look at your own second example, you will see that it doesn't do what it should do
(if `Fiber.yield` is replaced with yield point of your scheduler... funny_falcon (Yura Sokolov)