Wdestroier
Wdestroier
I get top-level inference with `late final foo = () => ...;` too. The logic to pick the return type must already exist. Could we have a package-wide setting to...
Considering I use inference most of the time, changing `int id = 1;` to mean `final int id = 1;` would not help (possibly make it worse), because I would...
> Some developers (me too) use `final` for top-level library fields You could write `myTopField := value;` instead of `final myTopField = value;` . That's an improvement for you too,...
> But what about late final variables? The syntax would be `late property := value;` I guess, and the same for static. Lasse proposed this syntax in the other issue,...
> The proposal was to make all the variables to be final by default without the need to write the 'final' keyword. The `int` class has a very short name,...
~~Apparently something all these examples have in common is they have 2 or more parameters.~~ Edit: @mateusfccp pointed [multiple-named-and-call](https://github.com/munificent/temp_arg_split_sample/commit/dea8aae491671c004e1799e610f7600822af0180) would fix the example below and apparently it's better than the...
The formatting of the ternary operator is taking so much space. 
I found an issue which looks related to the new Flutter proxy and webdev, but I changed back to Vite. I updated Flutter to the latest version (3.38.1) and I'm...
1. Vite (vite 4.5.3, vite-plugin-mkcert 1.17.5, Node.js 19.9.0) 2. `vite.config.ts` ```ts import { defineConfig } from 'vite' import mkcert from 'vite-plugin-mkcert' const path = require('path') export default defineConfig(({ command, mode...
> I still think we want to use the second approach. Examples: ```dart class V(int x, int y); augment class V(x, y) { // line 3 final double magnitude =...