зеркало из https://github.com/github/ruby.git
b9332ac8e7
I noticed this while running test_yjit with --mjit-call-threshold=1, which redefines `Integer#<`. When Ruby is monkey-patched, MJIT itself could be broken. Similarly, Ruby scripts could break MJIT in many different ways. I prepared the same set of hooks as YJIT so that we could possibly override it and disable it on those moments. Every constant under RubyVM::MJIT is private and thus it's an unsupported behavior though. |
||
---|---|---|
.. | ||
codeql | ||
workflows | ||
SECURITY.md | ||
auto_request_review.yml | ||
dependabot.yml |