language
language copied to clipboard
dart-lang
Design of the Dart language
[Updated: This was an overly terse summary, which caused some confusion. I've elaborated (hopefully more clearly) [here](https://github.com/dart-lang/language/issues/2378#issuecomment-1206942027)] The current rules for switches require that constants in switches come from classes...
I find dart constructors initializer list often hinder readability and needlessly redundant when trying to have private members. They are also [sometimes annoying to read in public api scenarios](https://github.com/dart-lang/language/issues/1613) I...
The records proposal specifies identity [here](https://github.com/dart-lang/language/blob/master/working/0546-patterns/records-feature-specification.md#identity) to be structural. In particular, identity is *required* to return `true` for any two records with the same shape for which the fields are...
(See https://github.com/dart-lang/language/issues/1290 for the similar questions for records.) Should there be a `Struct` type which all `struct` declarations implicitly implement, and which no non-`struct` type can implement? It allows *recognizing*...
Named mixins
Add syntax for named mixins to be able to reuse some logic dependent on class life-cycle. This feature might be a good fit for an ongoing discussion here https://github.com/flutter/flutter/issues/51752 some...
This is a meta-issue to collect up discussion around a proposal I've landed [here](https://github.com/dart-lang/language/blob/master/working/extension_structs/overview.md). This issue is intended to capture broad discussion about the approach. Specific points of discussion around...
The proposal says > Each field is a type annotation and an optional name which isn't meaningful but is useful for documentation purposes. Can we consider starting without this as...
In response to #92, about the use of `==` vs. `identical` to detect that two instances of type `Type` reify the same type, we specify that `Type` instances that constantly...
The records proposal forbids using private names in a record: ``` A field name that starts with an underscore. If we allow a record to have private field names, then...
The proposal for tuples have a `Record` class which acts as a common supertype of tuple types. Whether that is necessary or desirable depends on perspective and features. The main...