Components of an RCR

Title

A short, succinct, non-joking title, indicating the change you are going to propose

Abstract

Slightly longer descriptive sentence or two, referring briefly to both the problem and your proposed solution

Problem

Description of the thing you believe is missing from Ruby, wrongly designed in Ruby, or in need of extended functionality. What difficulties have been caused by the problem you are describing?

Proposal

An exact description of the Ruby change you are proposing: how it will affect syntax and/or semantics, what it will add to or remove from the language, which source or library files will be affected. If it involves visible language change, include before-and-after code examples.

Analysis

Why does the problem demand a language-level change? Why does your proposal best solve the problem? This is where you should make the case for the "fit" between the problem you perceive and the solution you are proposing.

Implementation (optional but encouraged)

An implementation, preferably in Ruby, of your proposed change. Not all RCRs lend themselves to implementation, but if yours does, you are strongly encouraged to implement it.


Back to RCRchive Help Center.

Back to RCRchive.