Lasse R.H. Nielsen
Lasse R.H. Nielsen
The package [stream_transformers](/dart-lang/stream_transform/) was created as an experiment. The API has now matured and stabilized, and it might make sense to include it in `package:async`, rather than having two different...
It's not documented anywhere how to link to non-trivial Dart entities. Simple `[prefix.class.member]` references, or relative `[nameInScope]` are easy (which scope is used should be documented, though), but it's not...
Changes I'd make (not all, but some). Easier than writing them out-of-line.
## Proposed change Zones define the concept of “error zones” and prevents some errors from flowing from a future in one error zone to a future in another. We will...
If we change the declaration of the `Function` class to `class Function` and special-case `Function` to mean the function type `int Function(int, int)`, and allowing `Function` to represent any function...
See [pattern proposal](https://github.com/dart-lang/language/blob/master/working/0546-patterns/patterns-feature-specification.md#constant-matcher). The constant matcher can be used to match specific values. It must be a constant value. This makes sense for when it's used in a `switch` `case`...
The current [records proposal](https://github.com/dart-lang/language/blob/master/working/0546-patterns/records-feature-specification.md#records-feature-specification) does not introduce a "spreading" operator. I think it should have one. A "record spread", with syntax `... recordExpression`, would be allowed inside any record expression...
In an `async` function with return type `Future`, Dart currently allow you to return either a `T` or `Future`. That made (some) sense in Dart 1, where the type system...
The current tuple proposal makes tuples immutable. I think that's great. However, there will be situations where, say, you have `(int, int, {Color: color}) cpoint;` and you want to change...