sylvain.joyeux (Sylvain Joyeux)

	open	closed	Total
Assigned issues	0	0	0
Reported issues	1	7	8

08:37 PM Ruby Bug #16853: calling bla(hash, **kw) with a string-based hash passes the strings into **kw (worked < 2.7): > If there is a call like foo(**h), and h has both Symbol and non-Symbol keys, in <2.7 the Hash is "split" which I find extremely confusing and it's also slowing things down by always having to consider "there might be an extra positiona... sylvain.joyeux (Sylvain Joyeux)

01:55 PM Ruby Bug #16853: calling bla(hash, **kw) with a string-based hash passes the strings into **kw (worked < 2.7): Hi Yusuke. Thanks for the long thought-out answer. I really appreciate you taking the time.
> But the behavior was changed to reject non-symbol keys, and it was done without matz's confirmation. So in a sense, this is a bug fix.
It... sylvain.joyeux (Sylvain Joyeux)

12:21 AM Ruby Feature #16891: Restore Positional Argument to Keyword Conversion: sawa (Tsuyoshi Sawada) wrote in #note-2:
> The core of that problem actually has nothing to do with allowing non-symbol keyword argument. That developer ad hocly used string vs. symbol distinction in hope that hash keys within a position... sylvain.joyeux (Sylvain Joyeux)

08:18 PM Ruby Bug #16853: calling bla(hash, **kw) with a string-based hash passes the strings into **kw (worked < 2.7): > This change was deliberate and mentioned in the 2.7.0 release announcement:
I missed this specific implication of that change ... Sorry for the noise. Thanks. sylvain.joyeux (Sylvain Joyeux)
12:00 PM Ruby Bug #16853 (Rejected): calling bla(hash, **kw) with a string-based hash passes the strings into **kw (worked < 2.7): The following code
~~~
def bla(hash = {}, **kw)
puts "H: #{hash}"
puts "K: #{kw}"
end
bla "some" => "string"
~~~
**silently** outputs the following (no warnings about deprecation of keyword parameters-from-hash)
... sylvain.joyeux (Sylvain Joyeux)

12:32 PM Ruby Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC): > Does it matter what the exact timeslice is in absolute units, or what matters is how often is a high-priority Thread executed compared to a low-priority Thread?
The actual underlying behavior matters, actually. If I'm using Linux sc... sylvain.joyeux (Sylvain Joyeux)

08:02 PM Ruby Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC): OK ... since it seems that everyone is camping on their own position, I have an alternative proposal: initialize the min and max priority values using environment variables on MRI, defaults to -3 and 3. Would that be alright ? sylvain.joyeux (Sylvain Joyeux)

05:25 PM Ruby Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC): > -5 would still mean "the highest priority", yes, but then e.g. -4 or -3 which starts to mean "high but not highest priority" on MRI would have a different meaning on other implementations, which I believe is undesirable.
-5 means "g... sylvain.joyeux (Sylvain Joyeux)

11:22 PM Ruby Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC): > I think it's important, otherwise how is Ruby code supposed to know what are the limits and which value it can use for Thread#priority= ?
It does not have to know. It will use, say -5 because it is meaningful on MRI. The value is th... sylvain.joyeux (Sylvain Joyeux)
05:05 PM Ruby Feature #15438: Threads can't switch faster than TIME_QUANTUM_(NSEC|USEC|MSEC): `RUBY_THREAD_PRIORITY_MIN` is changed to give the developer the choice to make some threads really low priority, at the cost of switching overhead. Unless I'm mistaken, the semantic of 'priority' right now is very platform-specific anywa... sylvain.joyeux (Sylvain Joyeux)

Also available in: Atom

Ruby Issue Tracking System