Michael Thomsen
Michael Thomsen
> Sounds like we should convert the lint to a warning so that it's always enabled. Yes, I think a roll-out plan like this might work: - Current: flagged by...
Thanks! 2.19 branching is several months away.
This would probably be useful to get the code migrated: https://github.com/dart-lang/sdk/issues/47219
@bwilkerson we've been doing a ton of cleanup. Can you try to run your CL checks again after rebasing?
If there were any updates, they would have been here in the issue already. Yes, it's been a year+, but there are only so many things we can work on,...
Could we: 1) leave it unspecified 2) in debug mode print `(${this.0}, ${this.1}, foo: {$this.foo})` for `(int, int, foo: int)` 3) in release mode print `(${this.0}, ${this.1}, _: {$this.foo})` for...
`facade class` is another option for `view`
@pq do we have a lint for this? We recently triaged [prefer_interpolation_to_compose_strings](https://dart-lang.github.io/linter/lints/prefer_interpolation_to_compose_strings.html), but that is for combining with plus, not just adjacency, I think?
Updated the description. This will be covered in much more detail in the actual proposal.
Related SDK issues: https://github.com/dart-lang/sdk/issues/34, https://github.com/dart-lang/sdk/issues/30347