Bob Nystrom

> There would be no feature ambiguity since function types don't have static namespaces. But they will if we do static extensions (#723), right? I really like the general idea...

No update. This doesn't seem to be something many users are clamoring for.

> Like the op, I want to export two classes with the same name under different directories from my library (Java-style namespaces). Dart obviously complains if I add both in...

Looks like CI is still (or again) failing: https://github.com/dart-lang/language/actions/runs/11263974170/job/31323025779?pr=4126

OK, I've taken a random sample of Dart code on pub and prototyped a few tweaks to argument splitting. The repo is [here](https://github.com/munificent/temp_arg_split_sample/branches). The main branch is formatted using the...

> Flutter-style declarative widget constructors tend to have _only_ named arguments. That's *mostly* true. `Text()` is the main exception. But this is a good observation. I went ahead and tried...

OK, I have tried many many heuristics and rules and I think I've found a couple that work well. They mostly split Flutter UI code without being hardcoded to look...

A labeled else block is also a little wonky, though honestly I'm not sure what the right output should be here: Before: ```dart main() { { { { if (c)...

I'm going to close this issue because I think https://github.com/dart-lang/sdk/issues/60119 does a good job of tracking the related linter work.

> It is similar, but that one was dropped because it used a syntax which is indistinguishable from record patterns. At least, I haven't heard anybody arguing in favor of...