[GR-19834] Prevent MatchData.allocate like MRI 2.7, but still let #dup and #clone work.

PullRequest: truffleruby/1168

Author: eregon

ci.jsonnet

@@ -239,7 +239,6 @@ local part_definitions = {
   platform: {
     linux: {
       platform_name:: "Linux",
-      "$.run.specs":: { test_spec_options: ["--excl-tag", "ci"] },
       "$.cap":: {
         normal_machine: ["linux", "amd64"],
         bench_machine: ["x52"] + self.normal_machine + ["no_frequency_scaling"],
@@ -253,7 +252,6 @@ local part_definitions = {
     },
     darwin: {
       platform_name:: "Darwin",
-      "$.run.specs":: { test_spec_options: ["--excl-tag", "darwinCi"] },
       "$.cap":: {
         normal_machine: ["darwin_mojave", "amd64"],
       },
@@ -280,9 +278,10 @@ local part_definitions = {
 
   run: {
     test_unit_tck_specs: {
-      run+: jt(["test", "unit"]) + jt(["test", "tck"]) +
-            jt(["test", "specs"] + self["$.run.specs"].test_spec_options),
-      # + jt(["test", "specs", ":next"]) disabled as it's currently empty and MSpec doesn't support empty sets of files
+      run+: jt(["test", "unit"]) +
+            jt(["test", "tck"]) +
+            jt(["test", "specs"]) +
+            jt(["test", "specs", ":next"]),
     },
 
     test_fast: {

doc/contributor/native-image.md

@@ -93,7 +93,7 @@ You can build a native build of TruffleRuby using the Native Image Tool from a
 source distribution using:
 
 ```bash
-$ jt build native
+$ jt build --env native
 ```
 
 The disadvantages of the Native Image version of TruffleRuby are:

doc/contributor/workflow.md

@@ -192,18 +192,18 @@ exception.
 When the spec is fixed the `untag` command will remove the tag and you can
 commit the fix and the removal of the tag.
 
-## Running specs for Ruby 2.5 features
+## Running specs for Ruby 2.7 features
 
-TruffleRuby currently targets Ruby 2.4. However, we welcome pull requests for
-Ruby 2.5 features as long as they don't conflict significantly with
-Ruby 2.4 semantics.
+TruffleRuby currently targets Ruby 2.6. However, we welcome pull requests for
+Ruby 2.7 features as long as they don't conflict significantly with
+Ruby 2.6 semantics.
 
-It is possible to run specs for Ruby 2.5 features by setting
+It is possible to run specs for Ruby 2.7 features by setting
 `PRETEND_RUBY_VERSION`:
 
 ```bash
-# Integer#digits is introduced in 2.5
-$ PRETEND_RUBY_VERSION=2.5.0 jt test spec/ruby/core/integer/digits_spec.rb
+# File.absolute_path? is introduced in 2.7
+$ PRETEND_RUBY_VERSION=2.7.0 jt test spec/ruby/core/file/absolute_path_spec.rb
 ```
 
 This also works for `jt tag`/`jt untag`.

spec/truffle.mspec

@@ -94,6 +94,7 @@ class MSpecScript
   ]
 
   set :next, [
+    "spec/ruby/core/matchdata/allocate_spec.rb",
   ]
 
   set :backtrace_filter, /mspec\//

src/main/java/org/truffleruby/builtins/CoreMethodNodeManager.java

@@ -373,8 +373,8 @@ private static RubyNode transformResult(CoreMethod method, RubyNode node) {
         return node;
     }
 
-    private void verifyUsage(DynamicObject module, MethodDetails methodDetails, final CoreMethod method,
-            final Visibility visibility) {
+    private void verifyUsage(DynamicObject module, MethodDetails methodDetails, CoreMethod method,
+            Visibility visibility) {
         if (method.isModuleFunction()) {
             if (visibility != Visibility.PUBLIC) {
                 RubyLanguage.LOGGER