Bob Nystrom

> I'd actually expect `:foo` to mean `:foo`, an absolute path into the current package. Me too. > Then > > ```dart > import :src/helper.dart > ``` > > _would_...

I'm personally not a fan of adding syntax that relies on a convention for organizing libraries that doesn't already exist. I think this convention is already pretty well-established: `widgets/button.dart` `widgets.dart...

I've written [a prototype fix flag in dart_style](https://github.com/dart-lang/dart_style/tree/temp-import-shorthand) that converts current URIs to the proposed shorthand syntax here when possible. You can run it like: ```sh $ git clone https://github.com/dart-lang/dart_style.git...

> If the value is Nullable the '?.' operator should always be used Not always: ``` dart obj.toString() // works even if obj is null ``` I think `.` should...

> It also reads more naturally in that position: ?int is "nullable int" and "!T" is "non-null T". Strangely enough, I actually like reading them mentally as punctuation. :) I...

> One could then make use of void as a type argument to futures as in Future. We've already got `Future` for that case (though in practice everyone just does...

> I do still currently feel that we should draw a line at allowing modification of the static shape of existing declarations. That line doesn't exist for users writing code...

Related: Allow a macro applied to a function to do something at every invocation site of the function. That could be nice for debug-only code so that the call can...

> I wasn't sure if it was better to compare based on top/left/bottom/right, or pos/size, but went with pos/size because those are externally visible Normally, I think that would be...

Thanks for hacking on this! > I didn't add a test case or mention the negative width/height thing because I'm not sure I understand how they're actually supposed to work...