You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file identifies the known V7 features, and tracks their status. Although there were minor "dot" releases of V7, committee ECMA TC49/TG2 plans to combine all 7.x features into one V7 spec.
For the most part, the features were spec'd in version-number order. (One exception was that a feature from 7.2 was combined with two related features from 7.0 in a single PR.) Dependencies between feature specs are noted. The Effort is an attempt to show the size/complexity of the proposal, such as small, *medium", or large, allowing TG2 to pick-and-chose the ones they'll work on next.
Unlike with the V6 work, where we had separate and divergent V5 Ecma and MS specs, for V7, we started with a set of MS proposals, some of which were placeholders for which text was never provided. Where they existed, Rex took these proposals, wrote tests, looked at MS (and other) tutorial pages, and created a brach, and for most features, a corresponding (Draft) PR, with the edits he thought were needed. It is quite possible that not everything in any given MS proposal was in fact implemented in that version, and it is also possible that things implemented in a version later on were not spec'd back into the proposal.
For any given feature, Rex actually wrote his version of the final proposal, in a Word file, but using md syntax. This allowed him to order the sets of edits by clause and subclause, and to exploit Word's comment, tracked-change, color, and other features, in order to make the proposal more readable and consistant. A Table-of-Contents was also added, so the reader can see at a glance the areas of the standard impacted by the proposal. This Word document was eventually turned into the branch edits and corresponding PR. For at least some features, it likely will be useful for TG2 members to have access to these Word files, as they may be helpful in seeing the actual changes made, along with "Notes to TG2" that I made fro consideration come processing time. (These Word documents and their associated test currently reside in a DropBox folder to which Bill Wagner has access, as well as on Rex's machine.)
The following features were combined: binary integer literals, embedded digit separators in numeric literals, leading digit separators in bin/hex integer literals.
The following features were combined: binary integer literals, embedded digit separators in numeric literals, leading digit separators in bin/hex integer literals.
The following features were combined: binary integer literals, embedded digit separators in numeric literals, leading digit separators in bin/hex integer literals.
V7 Feature List and Current Status
This file identifies the known V7 features, and tracks their status. Although there were minor "dot" releases of V7, committee ECMA TC49/TG2 plans to combine all 7.x features into one V7 spec.
For the most part, the features were spec'd in version-number order. (One exception was that a feature from 7.2 was combined with two related features from 7.0 in a single PR.) Dependencies between feature specs are noted. The Effort is an attempt to show the size/complexity of the proposal, such as small, *medium", or large, allowing TG2 to pick-and-chose the ones they'll work on next.
Unlike with the V6 work, where we had separate and divergent V5 Ecma and MS specs, for V7, we started with a set of MS proposals, some of which were placeholders for which text was never provided. Where they existed, Rex took these proposals, wrote tests, looked at MS (and other) tutorial pages, and created a brach, and for most features, a corresponding (Draft) PR, with the edits he thought were needed. It is quite possible that not everything in any given MS proposal was in fact implemented in that version, and it is also possible that things implemented in a version later on were not spec'd back into the proposal.
For any given feature, Rex actually wrote his version of the final proposal, in a Word file, but using md syntax. This allowed him to order the sets of edits by clause and subclause, and to exploit Word's comment, tracked-change, color, and other features, in order to make the proposal more readable and consistant. A Table-of-Contents was also added, so the reader can see at a glance the areas of the standard impacted by the proposal. This Word document was eventually turned into the branch edits and corresponding PR. For at least some features, it likely will be useful for TG2 members to have access to these Word files, as they may be helpful in seeing the actual changes made, along with "Notes to TG2" that I made fro consideration come processing time. (These Word documents and their associated test currently reside in a DropBox folder to which Bill Wagner has access, as well as on Rex's machine.)
out
variablesout
variables, Discards, use expression variables in more locationsout
variables, Discards, use expression variables in more locations==
and!=
with tuple types.ref
locals and returnsthrow
Expressionsasync
return typesasync Main
methoddefault
literal expressions==
and!=
with tuple types.private protected
access modifierref
expressionsin
parameter modifierref
withthis
in extension methodsreadonly
andref
structsref
local variablesstackalloc
arraysfixed
Statements==
and!=
with tuple types==
and!=
with tuple types.out
variables, Discards, use expression variables in more locations. LargeThe text was updated successfully, but these errors were encountered: