Modestas Valauskas

Thank you Lasse for the more detailed analysis of both styles. > But, as munificent said, we've gone down this road, we should take it to its conclusion and allow...

> I'd also be fine with fixing initializer lists at the same time Here is an example of what that could look like: ```dart class Foo { final int i;...

That would be great. Especially when using VillainAnimations during the lifecycle of a page e.g. animating datatable entries when the data has changed.

iOS forbids JIT compilation. According to wasmer, wasm files will have to be precompiled to dylibs when running on iOS devices. Therefore, I think we won't be able to just...

The smaller grammar by Storyyeller [on grammophone](https://mdaines.github.io/grammophone/?s=UyAtPiAiYSIgRSAiYyIKICAgfCAiYSIgRiAiZCIKICAgfCAiYiIgRiAiYyIKICAgfCAiYiIgRSAiZCIuCkUgLT4gIngiLgpGIC0+ICJ4Ii4=) It looks pretty much like the grammar from https://github.com/lalrpop/lalrpop/issues/768#issuecomment-1787079315 so that issue and this one are possibly duplicates.

I'm closing this issue because it is stale.

I've proposed the idea of `explicit control flow` here: https://github.com/dart-lang/linter/issues/4054. Under a policy that enforces "explicit control flow" `exit(...)` would have been highlighted as implicit control flow. Fixing implicit control...

> It could be a while. @srawlins No worries, thank you for taking a look into this.

> Dart has always had implicit control flow because of exceptions. [...] it wouldn't be possible to add an explicit throw before every potentially non-returning method. @bwilkerson thank you for...

I think that, rather than calling it "dead" (as in dead code) or "unnecessary" (as in useless), it would be more useful to call it "redundant". Redundancy can be bad,...