Feature #21768: Remove deprecated functions

• Status: Open
• Assignee: -
• Target version: 4.1

[nobu (Nobuyoshi Nakada)]

There many deprecated functions.
Why we carry them over the new major version?

Functions to be removed:

• rb_clear_constant_cache deprecated for 3 years
• postponed job APIs deprecated for 2 years
• old APIs to allocate a data object deprecated for 5 years
• rb_complex_polar deprecated for 7 years
• rb_clone_setup and rb_dup_setup deprecated for 4 years
• rb_gc_force_recycle deprecated as "removed soon"
• taintedness/trustedness enums/macros deprecated for 4 years
• RUBY_FL_DUPPED deprecated for 4 years
• rb_iterate deprecated since 1.9
• struct RData deprecated by struct RTypedData

https://github.com/ruby/ruby/pull/15447

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[jhawthorn (John Hawthorn)]

To me it seems too close to the release to make this kind of breaking change. Maybe we can consider it for Ruby 4.1 instead? It would be nice if removals made it into a -preview release.

[byroot (Jean Boussier)]

I agree with John, we're very close to release, even more so if you consider a lot of people will be away and checked out over the holidays almost a week before release.

However I do absolutely agree that the C API is full of deprecated things we should really consider removing, but also there are a lot of things that were inadvertently exposed and that we should consider deprecating.

I think we should do this right after 4.0 is released, so that downstream project have a whole year to react and prepare (or ask for things to be re-instated if they are actually worth it).

[nobu (Nobuyoshi Nakada)]

• Tracker changed from Misc to Feature
• Target version set to 4.1