Successor ML:Community Portal
From Successor ML
Directions for successor ML
Standard ML is different things to different people. Some viewed it as a vehicle for research in programming languages and compilers. Some consider it an important part of the education of young computer scientists. Some find it to be the best-balanced software development platform for experimental or production programming.
Whether all of these goals, and in what proportion, are considerations for successor ML generations, has not yet been established. This seems to require a project page, tentatively named Directions.
Request For Change (RFC)
The following is a draft proposal for the format of a Successor ML RFC should be. An RFC should be organized into the following sections:
- Introduction -- a summary of the proposal
- Motivation and examples -- why is the proposal a good idea; how is it used.
- Assumptions. What other extensions are assumed to be available.
- Formal syntax.
- Formal static semantics.
- Formal dynamic semantics.
- Interactions with previous proposals and other language features. This section should include any impact on the base-line definition of Successor ML.
- Porting issues. How would existing implementations and user code be affected?
- Implementation issues.
Furthermore, before a RFC is approved for inclusion in the Successor ML definition, there must be at least two conforming implementations of the RFC.
Page Organization
See the 'Help' page for now.
