Project

General

Profile

Actions

Feature #17490

closed

Rename RubyVM::MJIT to RubyVM::JIT

Added by k0kubun (Takashi Kokubun) over 1 year ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:101809]

Description

Background

These days it's sometimes said that CRuby may add another lightweight JIT. Leaving RubyVM::MJIT under such a situation might imply RubyVM::MJIT will not impact the future JIT, but I think MJIT.pause/MJIT.resume should impact all JITs by default if --jit is going to enable all the JITs. The current naming will be confusing, and I think these features should named consistently with --jit.

I also think, although this feature is for JIT developers anyway, we should not add many APIs to control JIT (for now I want JIT to be a feature where users don't need to think about tuning it, and having such APIs might end up letting people do that), and this naming change will contribute to discouraging APIs for a particular JIT.

Proposal

Have the same constant as RubyVM::JIT, deprecate RubyVM::MJIT from Ruby 3.1, and remove the old one in Ruby 3.2.

Impact

This impacts only [Feature #14830] RubyVM::MJIT.pause / RubyVM::MJIT.resume, which is basically for k0kubun's own testing.


Related issues 1 (0 open1 closed)

Related to Ruby master - Feature #18349: Let --jit enable YJIT on supported platformsClosedActions
Actions

Also available in: Atom PDF