Proposals
These are formal proposals for changes to the language specification or the standard library. They are called FEPs (that is, Flect Enhancement Proposals). See [FEP 000](Proposal 000 - Flect Enhancement Proposal Template) for a template and [FEP 001](Proposal 001 - Flect Enhancement Proposal Example) for an example.
Proposals start out in a draft form. From there, they can move to being finished or being superseded by another proposal (a finished proposal cannot be superseded). Draft and finished proposals may be withdrawn by the author. When a proposal is finished, it will be reviewed by the Flect developers and be either accepted or rejected. If the proposal is accepted, it can then be implemented. If a proposal reaches a state of superseded, withdrawn, accepted, or rejected, it is permanent (rare exceptions may be made in the case of accepted proposals where a severe flaw is found). So, if a proposal has been superseded, withdrawn, or rejected and a new, better design is thought up, a new proposal should be made.
A proposal should start with Proposal XXX: in the page title and be linked to verbatim (where the XXX is the proposal number). Remember to move a proposal to an appropriate section below when its status changes.
- Home
- Introduction
- Motivation
- Features
- Tutorial
- Library
- FAQ
- General
- Interoperability
- Syntax
- Type System
- Macros and CTE
- Specification
- Introduction
- Lexical
- Common Grammar Elements
- Modules and Bundles
- Type System
- Declarations
- Expressions
- Macros
- Compile-Time Evaluation
- Memory Management
- Application Binary Interface
- Foreign Function Interface
- Unit Testing
- Documentation Comments
- Style
- Indentation
- Braces
- Spacing
- Naming