Switch branches/tags
Nothing to show
Find file History
Permalink
..
Failed to load latest commit information.
csharp-7.0 Add draft spec for pattern-matching in C# 7. (#1778) Aug 13, 2018
csharp-7.1 Update LDM history Feb 16, 2018
csharp-7.2 Merge pull request #1658 from bbarry/patch-4 Aug 10, 2018
csharp-7.3 Merge pull request #1501 from hyagli/patch-1 Jul 29, 2018
csharp-8.0 More PR Comments Apr 17, 2018
inactive Add folders and READMEs Jan 27, 2017
rejected Add folders and READMEs Jan 27, 2017
README.md Update READMEs for discussion in GitHub issues Feb 14, 2017
async-streams.md should implement IAsyncDisposable correctly (#1250) Jan 25, 2018
caller-argument-expression.md Fix typos in `proposals` (#1267) Jan 25, 2018
covariant-returns.md Add proposal for covariant return types. (#47) Feb 9, 2017
declaration-expressions.md Add declaration-expressions.md proposal (#977) Oct 17, 2017
default-interface-methods.md Fix typos in `proposals` (#1267) Jan 25, 2018
fixed-sized-buffers.md Fix typos in `proposals` (#1267) Jan 25, 2018
intptr-operators.md Typo (#566) May 15, 2017
intrinsics.md Move proposal to the right folder Jul 19, 2018
lambda-attributes.md Add comment about return-targeted attributes Mar 29, 2017
null-coalescing-assignment.md the -> and Jul 19, 2018
null-conditional-await.md Update null-conditional-await.md Mar 15, 2017
nullable-enhanced-common-type.md Rename improved-common-type.md to nullable-enhanced-common-type.md Apr 20, 2017
nullable-reference-types.md Add design notes Oct 6, 2017
patterns.md Corrected patterns.md to use discard pattern ('_') in examples instea… Jun 5, 2017
proposal-template.md Remove abbreviations from the text (#68) Feb 13, 2017
ranges.cs Create ranges.cs May 8, 2018
ranges.md Update range proposal (#1770) Aug 6, 2018
readonly-instance-members.md Adding the readonly-methods proposal document. Jul 26, 2018
readonly_locals.md Add proposal for readonly locals Apr 4, 2017
records.md Multiple typos (#565) May 15, 2017
skip-localsinit.md fix summary Dec 28, 2017
static-delegates.md Clarifying on some points in the static-delegates proposal. Feb 16, 2017
target-typed-new.md Create target-typed-new.md (#1306) Mar 17, 2018

README.md

C# Language Proposals

Language proposals are living documents describing the current thinking about a given language feature.

Proposals can be either active, inactive, rejected or done. Active proposals are stored directly in the proposals folder, inactive and rejected proposals are stored in the inactive and rejected subfolders, and done proposals are archived in a folder corresponding to the language version they are part of.

Lifetime of a proposal

A proposal starts its life when the language design team decides that it might make a good addition to the language some day. Typically it will start out being active, but if we want to capture an idea without wanting to work on it right now, a proposal can also start out in the inactive subfolder. Proposals may even start out directly in the rejected state, if we want to make a record of something we don't intend to do. For instance, if a popular and recurring request is not possible to implement, we can capture that as a rejected proposal.

The proposal may start out as an idea in a discussion issue, or it may come from discussions in the Language Design Meeting, or arrive from many other fronts. The main thing is that the design team feels that it should be done, and that there's someone who is willing to write it up. Typically a member of the Language Design Team will assign themselves as a champion for the feature, tracked by a Champion issue. The champion is responsible for moving the proposal through the design process.

A proposal is active if it is moving forward through design and implementation toward an upcoming release. Once it is completely done, i.e. an implementation has been merged into a release and the feature has been specified, it is moved into a subdirectory corresponding to its release.

If a feature turns out not to be likely to make it into the language at all, e.g. because it proves unfeasible, does not seem to add enough value or just isn't right for the language, it will be rejected. If a feature has reasonable promise but is not currently being prioritized to work on, it may be declared inactive to avoid cluttering the main folder. It is perfectly fine for work to happen on inactive or rejected proposals, and for them to be resurrected later. The categories are there to reflect current design intent.

Nature of a proposal

A proposal should follow the proposal template. A good proposal should:

  • Fit with the general spirit and aesthetic of the language.
  • Not introduce subtly alternate syntax for existing features.
  • Add a lot of value for a clear set of users.
  • Not add significantly to the complexity of the language, especially for new users.

Discussion of proposals

Feedback and discussion happens in discussion issues. When a new proposal is added to the proposals folder, it should be announced in a discussion issue by the champion or proposal author.