Erik Ernst
f071f7ce64
Change-Id: I23c7e77ac64ce2cad288f42505ccf07257f00abc Reviewed-on: https://dart-review.googlesource.com/71861 Reviewed-by: Lasse R.H. Nielsen <lrn@google.com>
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
### This directory contains feature specifications.
|
|
|
|
**Note**: This directory contains older feature specifications, new ones
|
|
should be submitted to the language repository
|
|
[here](https://github.com/dart-lang/language).
|
|
|
|
The existing feature specifications in this directory will have their status
|
|
updated as we proceed, and in particular each of them will become 'background'
|
|
material as it is integrated into the language specification. When all feature
|
|
specifications in this directory (that is, all other files than this one) have
|
|
become background material, this directory will serve only as documentation for
|
|
the process whereby each feature was designed and the associated motivation.
|
|
|
|
That said, the following section contains a few words about what a feature
|
|
specification is, and how it can be used.
|
|
|
|
### What is a Feature Specification?
|
|
|
|
In order to move faster and get better feedback, we implement and iterate on
|
|
language changes before the full official specification has been written. Still,
|
|
the implementers need *something* to go on.
|
|
|
|
For that, the language team writes _feature specifications_. These are
|
|
intended to be precise enough for a good faith implementer to correctly
|
|
understand the syntax and semantics of the language, but when the contents
|
|
of a feature specification is integrated into the language specification we
|
|
expect the extra processing to give rise to additional clarifications and
|
|
corrections, which means that a feature specification is expected to be
|
|
_nearly_ as complete and correct as the language specification.
|