Lasse R.H. Nielsen

Results 152 issues of Lasse R.H. Nielsen

It's inconvenient that declaring final variables require more typing than non-final variables. This discourages the use of final variables. Even with inferred types, it's shorter, and if you want to...

request

This is an attempt to specify how nested part files with imports, and parent file import inheritance, should work. This assumes that part files can contain import, export and part...

feature
augmentation-libraries

Macros are run at a time when not all declarations exist, because some have yet to be introduced by macros. That means that any identifier that is being resolved by...

question
static-metaprogramming

Currently macros are Pub dependencies like any other. That, among other things, mean that their dependencies are the same as the dependencies of the user package. If both depend on...

request
static-metaprogramming

The current API for introspecting the source of the code that the macro is generating augmentations for, is fairly coarse-grained. The [example](https://github.com/jakemac53/macros_example) requests all methods from a class, then manually...

request
static-metaprogramming

See more detailed proposal here: https://github.com/dart-lang/language/blob/master/working/0884/interface_default_methods_proposal.md Adding new members to an interface is a breaking change in Dart, for several reasons. One reason is that a subclass might already implement...

feature

The [patterns proposal](https://github.com/dart-lang/language/blob/master/working/0546-patterns/patterns-feature-specification.md#switch-expression) includes an expression switch. It would likely be very useful to allow it as an "element switch" as well, so that it can be used in collection...

patterns
feature-completeness

Dart has implicit coercion only in very few cases: Implicit `call`-tearoff, implicit generic instantiation, and (arguably) implicit downcast from `dynamic` (which doesn't coerce anything, the value doesn't change). A fairly...

feature

When you start switching over sealed type hierarchies, it's incredibly easy to write: ```dart case TheType: .... ``` when you mean to do a type check for `TheType`. Instead it...

patterns

We allow `if (e case p when e) ...` as statements and elements, but not in as expressions, where conditional branching uses the `?`/`:` operator. I suggest we allow it,...

feature
patterns