Konstantin Scheglov
Konstantin Scheglov
`co19/LanguageFeatures/Records/record_expressions_A05_t02`
`co19/LanguageFeatures/Records/record_type_annotations_A05_t05`
See `co19/LanguageFeatures/Records/record_type_annotations_A04_t06`
Also `co19/LanguageFeatures/Records/record_type_annotations_A01_t04`
> Is it possible to catch the @deprecated when the value is assigned? > > ```dart > test2() { > (String, {int n}) x = foo(); // HINT: `.n` is...
> The problem with annotations is that they are at _source_ concept. It matters where they occur in the source, whether that corresponds to a static or runtime concept. That...
> Is the issue here that the analyzer model for a declaration has a "type" for the return type, which is a semantic entity, not a representation of the return...
Looking on the motivation in the [specification](https://github.com/dart-lang/language/blob/master/working/0546-patterns/records-feature-specification.md), I see three reasons: (1) no behavior, (2) verbosity, and (3) coupled to a class definition. Surprisingly, I don't see performance, i.e. I'd...
See `17.9 Switch` in the specification.  `Null` is not an instance of the class `MyEnum`. ```dart // @dart = 2.7 enum MyEnum { a, b } void f(MyEnum e)...
The way the spec is written, the code with `case null` has a compile-time error.