Michel Feinstein

If this is the case, then having a `try with resources` that `catch` `Exception` thrown inside the creation of the `Resource`, the execution of the computation or the closing of...

Wouldn't it run into the same issue? I think we would expect a runtime exception or a compile time warning, if we tried to access a variable inside a pattern...

@munificent could we get a `formatter` flag to configure which files (glob list) can be excluded from formatting? Maybe a `// dart format exclude` comment also? This will be useful...

> Otherwise, passing the list of generated files everywhere is going to be very complicated. I mean more something like: ```yaml # in analysis_options.yaml formatter: exclude: - "**/*.freezed.dart" - "**/*.g.dart"...

I agree with this, but then we need the package maintainer to add this to their generated files, and sometimes they don't and we can't control this. So I think...

I tried both packages and neither solved the issue. `FlexibleWrap` appears to have a bug, it is ignoring the `spacing` parameter, and it also lacks a `runSpacing` parameter. All my...

I can see 2 possible scenarios that could be desirable for this new proposed behaviour for `Wrap`: 1. All widgets take the same width, if one can't then it goes...

I added `tryUniformWidth` into https://pub.dev/packages/flex_list which solved this issue for me, but I think this should still exist in Flutter.

Having something as: ``` mixin A with B { void methodFromA() { methodFromB(); } } ``` Would be a very nice refinement on the language

How about `fakeAsync.await(myFuture)`? I don't think this will cover stream cases, but internally the library could pump the event loop unit that future completes, using a completer maybe.