Development of language specification (was typedef alive and well?)

Martin Nowak dawg at dawgfoto.de
Fri Nov 4 09:10:56 PDT 2011


Moved to an extra thread, so it won't get lost.

I propose the following process using the language specifications at  
github:d-programming-language.org.

- The language specifications are made version specific (e.g. 2.6, partly  
handled by tags already).

- Branches are created for the next 2(?) minor versions ahead of the  
current release cycle.
   Another one is created for the next major version.

- The website should have links to specifications for different versions
   which are build from the corresponding tags/branches.

- We adopt a pull based development for the language specification similar
   to that for phobos (review queue, review manager, voting).

- Specs are lined with acceptance tests. Ideally this would be the code  
examples.

- The compiler strives to fulfill the specs on corresponding versions.

- Specs are added to the autotester.

Not sure if github:d-programming-language.org can handle all this  
appropriately,
but it seems worth a try.


As a first test case someone could salvage the abbreviated delegate syntax  
(a => a+2).

martin


More information about the Digitalmars-d mailing list