Accepted Features

[floitschG]

This bug tracks the accepted features for the language and libraries.
These are tentatively accepted features. This list is bound to change based on implementation complexities, new feedback, or unexpected corner-cases and interactions.

• Read-only access to initializing formals Allow read-only access to initializing formals. #26655
• &&= and ||=: Support "&&=" and "||=" operators #26996
• Assert accepts message. Implement assert() messages #24213
• Type instance is checks: o is expr. "is" operator should support an expression on the right hand side #27680
• resolved part-of. Allow "part of" to refer to its parent library by URI instead of name. #20792, Resolved Part-Of directives dart-archive/dart_enhancement_proposals#45
• allow incomplete unicode surrogate pairs in string literals. For example "\ud8xx". The escape sequence \uD is not valid code point #26620
• Take advantage of negative is-checks for type propagation. Work with dart2js and Analyzer teams to get proposal.
• asserts should allow assignment expressions: assert(x = true). Most implementations already did this.
• Optional new (see https://gist.github.com/floitschG/0a79d90c7824f3d540163b6ce7623236#file-optional_new-md)
  Make new optional #20750
  • const context const at the top level of a structure should propagate down #4046
  • constructor tear-offs
• positional and named optional parameters for the same function. Full optional parameters - both kinds on the same function. dart-archive/dart_enhancement_proposals#26 - next is requesting feedback from implementors.
• Allow "_" in number literals: Number literal syntax - allow underscores or other way to make number more readable #26845
• Allow void as generic argument: Allow "void" as a type argument #27504
• ?. should count for the rest of the selectors (o?.x.y should be correct) ?. operator should extend to remaining selectors #26240
• Generic arguments to constructors: https://github.com/dart-lang/sdk/issues/26391

[munificent]

@floitschG, are you still using this issue to track anything? If not, want to close it?

[floitschG]

It is still used.

[munificent]

Closing this because we aren't using this issue to track language work anymore.