stuartmorgan-g

There is a lint, but that doesn't do a very good job of addressing some use cases (like example code); see https://github.com/dart-lang/language/issues/1547#issuecomment-812515811 and my reply.

Yes, we had this conversation already above; [this earlier comment](https://github.com/dart-lang/language/issues/1547#issuecomment-831391330) explains why I don't think "everyone makes their own cast operator" is a good solution to the general problem.

> I cannot reproduce the hang with the sample file. Instead I get the following That may indicate that you don't have the necessary file-read permissions on your app, which...

Currently the way the plugin is designed, `initialize` completion is driven by event channel callbacks rather than an async method channel response, which makes it easy to never resolve the...

FYI, Apple explicitly reserves all two-letter prefixes for their own use (per the documentation linked above), so while you've avoided potential conflicts with future Flutter-team-authored code, you are now subject...

I would urge you to consider the fact that the new situation is significantly more dangerous than the one you fixed with the change. Previously a collision could only have...

> I've been doing this for over 9 years without issue. Yes, the nature of this class of problems is that it works fine as long as there are no...

> @Sfshaza I'd love to see some updates to our background docs. > > We currently have these two: https://docs.flutter.dev/cookbook/networking/background-parsing https://docs.flutter.dev/packages-and-plugins/background-processes > > But they are not cross-linked, and it's...

> Controller should be different for different window. > [...] > Controllers and runJavaScript and other method should not be conflict for different Class. The issue description is describing this...

Wait, so is the design doc out of date? I thought the plan was to move forward with the starred options in the doc, but that includes: > 3. There...