Bob Nystrom
Bob Nystrom
I'm up for making some kind of change here, but I want to make sure we do so while keeping in mind #4172. There's already weird irregularities in the language...
This is an old problem that's been around as long as [the Observer pattern](https://en.wikipedia.org/wiki/Observer_pattern) has existed. I remember dealing with it in C# WinForms apps in the early 2000s. If...
My preferred approach for this is still #2563 because it's maximally terse. You're right that we could use a leading `.` similar to dot shorthands, but that feels like a...
> > if the last line of a block is a valid expression, act as if it has a return keyword at the front > > no more. no less....
> A nice trade-off would be to only have implicit returns if there is only a single expression. In Dart, that's: ``` int get number => 42; ```
> Note, changing it this way would _not_ introduce any new syntax, it would just make the existing syntax work the way a user would expect. (Puts on pedantic hat.)...
Personally, I don't think these operators are very useful outside of if conditions, `||`, `&&`, and `!`. A simpler solution might be to treat `null` as falsey like most other...
True, but non-nullable types will likely catch most of those statically.
> What if I want to check a function variable is not null, then call it? We have discussed supporting `.?()` for that case: ```dart foo.bar?.(); ``` I'm not sure...
> cc @munificent - I think the formatter will always fail to resolve out-of-package includes right? Should we be suppressing this in the formatter output? I'm not sure what you...