shugo (Shugo Maeda)

	open	closed	Total
Assigned issues	3	159	162
Reported issues	3	95	98

Project	Roles	Registered on
Ruby	Committer, Infrastructure team	05/28/2008

09:55 AM Ruby Bug #22462: Method#== can return false for methods that should be considered equal: As I commented in https://github.com/ruby/ruby/pull/19474#pullrequestreview-5609342827, with the PR change, `==` UnboundMethods can bind to non-`==` Methods:
```ruby
module M; def m = [:M, *super]; end
class Base; def m = [:Base]; e... shugo (Shugo Maeda)

06:09 AM Ruby Feature #22309: Allow super in a module method to work if method was called by refinement method super: Thank you. I've confirmed that the leak is gone and that crefs with the same refinements now share iclasses, and I've approved https://github.com/ruby/ruby/pull/18910. shugo (Shugo Maeda)

05:19 AM Ruby Feature #22309: Allow super in a module method to work if method was called by refinement method super: Sorry for the confusing wording. By "the other refinements" I meant the other refinements in the chain copied from the caller's cref, which `vm_search_normal_superclass` skips since d3774085aa. The refinements in scope at the `super` cal... shugo (Shugo Maeda)

08:15 AM Ruby Feature #22392 (Rejected): Allow refinements to define && and ||: Thank you for the discussion at the developer meeting.
At the meeting, mame suggested an alternative: `lhs && rhs` as `lhs.&&() { rhs }`, which I had rejected myself before proposing this.
Anyway, I understand that it is difficult to... shugo (Shugo Maeda)
06:52 AM Ruby Feature #22309: Allow super in a module method to work if method was called by refinement method super: One addition: since the cache is a Hash, refinements and their iclasses would be retained even after they are no longer needed. Making both the key and the value weak would avoid this; maybe `ObjectSpace::WeakMap` in weakmap.c could be u... shugo (Shugo Maeda)
03:52 AM Ruby Feature #22309: Allow super in a module method to work if method was called by refinement method super: I have approved https://github.com/ruby/ruby/pull/18910, but there is one thing I am concerned about.
The cache entries are keyed by the refinement iclass of each cref and never removed, so each `using` scope or `Proc#refined` copy that... shugo (Shugo Maeda)

12:35 PM Ruby Feature #22392: Allow refinements to define && and ||: alanwu (Alan Wu) wrote in #note-6:
> BTW, the cost analysis to non-users is incomplete in the PoC.
You're right that the analysis is incomplete.
As you say, a parse-time switch would be ideal, but I cannot think of a way to do that ... shugo (Shugo Maeda)
02:28 AM Ruby Misc #22394: DevMeeting-2026-10-07: * [Feature #22392] Allow refinements to define && and || (shugo)
* I propose to allow `&&` and `||` to be defined in refinements, so that DSLs can write `where { name == "x" && age > 20 }` instead of `where { (name == "x") & (age > 20... shugo (Shugo Maeda)

07:53 AM Ruby Feature #22392: Allow refinements to define && and ||: alanwu (Alan Wu) wrote in #note-1:
> Please no. Changing non-method call operations to be method calls has disastrous time and space cost for everyone involved, JIT or not. If accepted, this would be yet another case of refinement makin... shugo (Shugo Maeda)

03:18 PM Ruby Revision 4c28391b (git): Keep a Monitor pinned while Monitor#enter blocks on its mutex: monitor_enter0() writes the owner and count after do_mutex_lock(),
which may block with the GVL released. The monitor was stored only in
a stack struct field that nothing read, which the compiler may drop, so
nothing was guaranteed to k... shugo (Shugo Maeda)

Also available in: Atom

Ruby Issue Tracking System