Skip to content
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.

Proposal 001: Flect Enhancement Proposal Example

Alex Rønne Petersen edited this page Jun 8, 2014 · 5 revisions
Author

Alex Rønne Petersen

Created

17-12-2012

Abstract

This is an example of an FEP (Flect enhancement proposal).

Motivation

There needs to be a process for enhancement proposals for Flect and its standard library.

Description

An Flect enhancement proposal (FEP) describes a proposed change to the Flect language or its standard library. It must include abstract, motivation, description, and rationale. Proposals that are finished will be reviewed by the Flect developers and be either accepted or rejected, and subsequently implemented if accepted. Draft proposals and finished proposals that haven't been implemented yet can be superseded by another proposal. Proposals that are in a draft state can also be withdrawn.

Rationale

This process is similar to the ones used by Python, Erlang, and D. It has been proven to work well in practice.

Compatibility

Not applicable.

Implementation

On the Flect wiki.

Copyright

This document is placed in the public domain.

Clone this wiki locally