From: "k0kubun (Takashi Kokubun)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:107155] [Ruby master Feature#17490] Rename RubyVM::MJIT to RubyVM::JIT
Date: Mon, 17 Jan 2022 06:32:15 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-96008.20220117063215.10073@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17490.20201230054510.10073@ruby-lang.org
Issue #17490 has been updated by k0kubun (Takashi Kokubun).
The revert was proposed and implemented at https://bugs.ruby-lang.org/issues/18349.
----------------------------------------
Feature #17490: Rename RubyVM::MJIT to RubyVM::JIT
https://bugs.ruby-lang.org/issues/17490#change-96008
* Author: k0kubun (Takashi Kokubun)
* Status: Closed
* Priority: Normal
----------------------------------------
## 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.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2022-01-17 6:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 5:45 [ruby-core:101809] [Ruby master Feature#17490] Rename RubyVM::MJIT to RubyVM::JIT takashikkbn
2020-12-30 15:05 ` [ruby-core:101812] " eregontp
2020-12-30 22:59 ` [ruby-core:101821] " nobu
2020-12-31 7:47 ` [ruby-core:101832] " takashikkbn
2020-12-31 8:05 ` [ruby-core:101833] " hsbt
2021-01-01 12:20 ` [ruby-core:101851] " eregontp
2021-01-01 12:48 ` [ruby-core:101853] " eregontp
2021-01-02 3:06 ` [ruby-core:101874] " takashikkbn
2021-01-02 12:50 ` [ruby-core:101879] " eregontp
2021-01-02 15:51 ` [ruby-core:101880] " takashikkbn
2021-01-03 13:28 ` [ruby-core:101886] " eregontp
2021-01-04 4:50 ` [ruby-core:101902] " takashikkbn
2021-01-13 6:29 ` [ruby-core:102051] " matz
2022-01-17 6:00 ` [ruby-core:107154] " znz (Kazuhiro NISHIYAMA)
2022-01-17 6:32 ` k0kubun (Takashi Kokubun) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-96008.20220117063215.10073@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).