22.4. Ruby Change Requests
Ruby continues to evolve. Part of its beauty is that it changes slowly and deliberately.
But Ruby is definitely not perfect. Therefore a mechanism is in place for users to suggest changes in Ruby’s syntax, its core classes, and its standard libraries. This is called the Ruby Change Request (RCR) process.
If you go to rcrchive.net (“RCR archive”), you will see a well-defined process (put in place by David Alan Black) allowing individuals to suggest changes, offer peer review or feedback, and even vote for or against those changes.
Before making a new RCR, first make sure that one like it does not exist. An identical RCR might be pending or might even have been rejected already.
Second, make sure you have dotted every ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access