File tree Expand file tree Collapse file tree 1 file changed +18
-0
lines changed Expand file tree Collapse file tree 1 file changed +18
-0
lines changed Original file line number Diff line number Diff line change 31
31
* [ How to tag slow ruby/spec tests] ( #how-to-tag-slow-rubyspec-tests )
32
32
* [ How to introduce a constant in specs] ( #how-to-introduce-a-constant-in-specs )
33
33
* [ How to add a new spec] ( #how-to-add-a-new-spec )
34
+ * [ How to work on a new CRuby feature] ( #how-to-work-on-a-new-cruby-feature )
34
35
35
36
## How to find a Core Method implementation
36
37
@@ -1564,3 +1565,20 @@ There are the following main directories:
1564
1565
- `spec/ruby/core` - specs for the Core Library
1565
1566
- `spec/ruby/library` - specs for the Standard Library
1566
1567
- `spec/ruby/language` - specs for the Ruby syntax itself
1568
+
1569
+ ## How to work on a new CRuby feature
1570
+
1571
+ When you work on a new feature/method usually you make the following steps:
1572
+
1573
+ - check a feature/method description in the Ruby documentation
1574
+ - check a corresponding issue (on the Ruby bug tracker <https://bugs.ruby-lang.org>):
1575
+ - a feature description
1576
+ - discussion
1577
+ - " Associated revisions" tab with commits and diffs (pay attention to added MRI and ruby/spec tests)
1578
+ - check existing ruby/spec tests in the TruffleRuby repository
1579
+ - add missing test cases
1580
+ - untag ruby/spec tests
1581
+ - implement the feature
1582
+ - untag MRI tests and ensure they pass too
1583
+ - mention in a PR description an original issue in a way it's described in the Ruby
1584
+ release notes or provide a link to an original ticket (on <https://bugs.ruby-lang.org>)
You can’t perform that action at this time.
0 commit comments