Ian Hickson

cc @sethladd is this done?

Ideally we'd just use whatever we tell other people to use, once we have an answer to that.

This still happens.

(Blocked on #718.)

My preference would be to experiment with codegen before we do anything with the language. Until a syntax becomes popular, I'd be reluctant to adopt anything here.

https://www.youtube.com/watch?v=dkyY9WCGMi0 explains why `build` is on `State` rather than on `StatefulWidget`.

@munificent How about: ```dart class Foo { Foo({ this.* }); final int bar; final int baz; } ``` ...or some such, where `this.*` (or whatever) implicitly means "all the fields"....

I'd be fine with requiring the use of named fields. But you could do something like: ```dart class Foo { Foo({ this.* }); final int bar; final int foo; }...

> I watched this presentation and some other videos on youtube, and I still have no idea why build method HAS TO be on State. It doesn't _have to be_...

The parent widget will create a new `WeatherReport` object every time it builds.