Lasse R.H. Nielsen

There would be no feature ambiguity since function types don't have static namespaces. I'm worried that using the same syntax for different things can lead to confusion. It's a nice...

> But they will if we do static extensions (https://github.com/dart-lang/language/issues/723), right? Unlikely. We should only allow static extensions on something that already has a static namespace. It's "static namespace extensions",...

Sounds like you need general namespaces. If you do `import 'src/lib.dart' as prefix;` you'd presumably have to write `prefix.foo.SomeClass` to access the class. We've so far kept Dart library exports...

Currently you would have to rename one of the classes. ``` import "src/some/foo.dart" as some; export "src/other/foo.dart" typedef SomeFoo = some.Foo; ``` You cannot export two declarations with the same...

You're not forced to write the return type everywhere. ```dart void main() { example() => (name: '', age: 42); print([example].runtimeType); // prints: List ({String name, int age})> } ``` This...

Null-safety was painful because the migration could not be automated. The new feature added (nullability-)information to the language that old programs didn't have, and new programs required. The migration was...

This does sound like a bug, relative to the current specification of [part files with imports](https://github.com/dart-lang/language/blob/main/working/augmentation-libraries/parts_with_imports.md). _It may be correct relative to the prior specification of augmentation libraries that this...

This sounds very much like "assets". Could something be shared? Or is it just an accident of both wanting to access bytes or strings? I can see a macro having...

> "Assets" (assuming you mean flutter assets) I mean Dart [data assets](https://github.com/dart-lang/sdk/issues/54003). They are also runtime only, but a macro that is running could use its own assets, or assets...

> And, we might also allow access from `lib/` to outside of `lib/` within the same package, but that is a little less clear. That has all the same issues....