diff options
| author | Benoit Daloze <eregontp@gmail.com> | 2023-10-30 13:49:46 +0100 |
|---|---|---|
| committer | Benoit Daloze <eregontp@gmail.com> | 2023-10-30 13:49:46 +0100 |
| commit | ab4781b64d945e962575f2eac20b72185235d23b (patch) | |
| tree | 9c4456926c1616b0417db0b389371d578876a136 /spec/ruby/CONTRIBUTING.md | |
| parent | 14fa5e39d72c84d3e12e10dc5d77a6e6200c10f5 (diff) | |
Update to ruby/spec@bd7017f
Diffstat (limited to 'spec/ruby/CONTRIBUTING.md')
| -rw-r--r-- | spec/ruby/CONTRIBUTING.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/spec/ruby/CONTRIBUTING.md b/spec/ruby/CONTRIBUTING.md index 4a1e1d46bd..c82eb5ea4f 100644 --- a/spec/ruby/CONTRIBUTING.md +++ b/spec/ruby/CONTRIBUTING.md @@ -179,6 +179,7 @@ In case there is a bug in MRI and the fix will be backported to previous version If it is not backported or not likely, use `ruby_version_is` instead. First, file a bug at https://bugs.ruby-lang.org/. The problem is `ruby_bug` would make non-MRI implementations fail this spec while MRI itself does not pass it, so it should only be used if the bug is/will be fixed and backported. +Otherwise, non-MRI implementations would have to choose between being incompatible with the latest release of MRI to pass the spec or fail the spec, both which make no sense. ```ruby ruby_bug '#13669', ''...'3.2' do |