Could the design document be made public?

My docs-fu is too weak, so I converted the design document it to a gist.

thanks

The doc defines the assert statement as being assert(expression), but the analyzer accepts an optional second argument. Is the omission an oversight, or should asserts in constructor initializers not allow a message?

We are going to add the second "argument" to assert, so keep it for now.

@lrhn can you please provide an update?

@lrhn can you provide an update?

FYI DDC issue #27809

This is not a 1.50 feature, so kicking out of the milestone. (I think we accidentally got it confused with assert messages, which are in 1.50).

This is done, right? flutter has this turned on now.

I'm not sure if this tracking issue is for the experiment or the feature. If the former, I guess it's closable? If the latter, no, because we haven't decided if we want to commit to it, remove the flag, etc.

oh gosh, yeah. Also DDC doesn't implement it yet, which I think nowadays we want for new language features? (it's not hard to implement btw)

This is a Flutter-only experiment (which is why it's VM+analyzer only so far, and should perhaps also include the formatter). That is all it is at this point. There is no decision to make it a language feature yet, it's not implemented by DDC or dart2js, and unless the experiment is a success, it will eventually be removed again.
The exact conditions for considering it a success isn't set in stone, but it should add non-negligible value for the Flutter developers. If it isn't, then it's just not worth its own weight.

The experiment has graduated to a feature. Closing out this bug in favor of #30968.

Thanks for the help!