Skip to content

Latest commit

 

History

History
8 lines (4 loc) · 563 Bytes

README.md

File metadata and controls

8 lines (4 loc) · 563 Bytes

Charj RFCs

Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow.

Some changes though are "substantial", and we ask that these be put through a bit of a design process and produce a consensus among the Charj community.

The "RFC" (request for comments) process is intended to provide a consistent and controlled path for new features to enter the language and standard libraries, so that all stakeholders can be confident about the direction the language is evolving in.