shugo (Shugo Maeda)
- Login: shugo
- Registered on: 05/08/2008
- Last sign in: 09/23/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 4 | 158 | 162 |
| Reported issues | 3 | 93 | 96 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Ruby | Committer, Infrastructure team | 05/28/2008 |
Activity
Today
-
11:33 AM Ruby Feature #22304 (Closed): Add rb_warn_to_remove_at() for deprecation warnings shown by default
- Applied in changeset commit:git|611bb146b08978aacb26bf4a4e8390e699628350.
----------
[Feature #22304] Add rb_warn_to_remove_at and rb_warn_scheduled_deprecation
rb_warn_deprecated_to_remove_at warns only when Warning[:deprecated]
is en... -
11:33 AM Ruby Revision 611bb146 (git): [Feature #22304] Add rb_warn_to_remove_at and rb_warn_scheduled_deprecation
- rb_warn_deprecated_to_remove_at warns only when Warning[:deprecated]
is enabled, so a deprecation scheduled to warn by default in a later
version needed a hand-written rb_warn and a separate commit to switch.
rb_warn_to_remove_at emits ...
09/20/2026
-
11:50 PM Ruby Feature #22304: Add rb_warn_to_remove_at() for deprecation warnings shown by default
- Dan0042 (Daniel DeLorme) wrote in #note-8:
> Does the updated target version need to be backported to every branch ?
There is a similar case. Ruby 3.3 still says "Process::Status#& is deprecated and will be removed in Ruby 3.4", althoug...
09/18/2026
-
10:19 PM Ruby Feature #22304: Add rb_warn_to_remove_at() for deprecation warnings shown by default
- Dan0042 (Daniel DeLorme) wrote in #note-6:
> Sorry for the trouble, but could you explain why "we should do anyway"? I might be missing something here.
A major version bump is a chance to introduce incompatibilities, so I think we shoul... -
12:21 PM Ruby Feature #22304: Add rb_warn_to_remove_at() for deprecation warnings shown by default
- Thank you for the idea. I think the API should keep the version numbers, because the warning message has to tell users the version ("will be removed in Ruby 4.3"), and a year cannot be converted to a version at compile time.
A major ver... -
04:50 AM Ruby Feature #22304: Add rb_warn_to_remove_at() for deprecation warnings shown by default
- I've created a pull request: https://github.com/ruby/ruby/pull/18904
-
01:42 AM Ruby Feature #22304: Add rb_warn_to_remove_at() for deprecation warnings shown by default
- In addition, how about a higher-level macro that takes both versions of the schedule?
```c
rb_warn_scheduled_deprecation(4.2, 4.3, fmt, suggest, ...)
```
Before 4.2 it warns only when `Warning[:deprecated]` is enabled, from 4.2 it warn...
09/17/2026
-
04:05 AM Ruby Bug #22276 (Assigned): alias in a module falls back to Object even in classes not inheriting from Object
- I've added a verbose-mode warning: https://github.com/ruby/ruby/pull/18740
-
03:37 AM Ruby Revision 1c0b1be0 (git): Deprecate the fallback to Object for alias in a module
- `alias` and `Module#alias_method` in a module fall back to searching
the method from Object when the module and its ancestors do not have
it. The fallback assumes Object is the root class, which is no longer
true since BasicObject was in...
09/14/2026
-
05:19 AM Ruby Feature #22309: Allow super in a module method to work if method was called by refinement method super
- jeremyevans0 (Jeremy Evans) wrote in #note-2:
> Do you think the VM frame flag for super calls, and fixing yjit/zjit to handle module refinements, would be sufficient?
I think a frame flag would fix the example I gave, but I do not see ...