Bob Nystrom
Bob Nystrom
OK, I'm going to close this. I'm OK with shipping support for records without special await support for them. (That means that awaiting a record just returns the record like...
I 1000% want any primary constructor syntax to be generalized to classes. In fact, I personally care more about that than I care about the entire views proposal. :) Most...
> This is assuming no changes to documentation conventions, which I think is not realistic. That's a good point. Hoisting all the field docs alleviates much of my readability concerns....
I'd be fine with saying you can't use structs with `Expando` and friends. Likewise records.
> In the meanwhile, there is a young library that generates sum-types (-alike classes) for you: https://github.com/werediver/sum_types.dart Thanks for mentioning this! This is a good reference for ensuring that whatever...
Thanks for the comment. I'm not sure if we literally want to build on Dart's existing enum syntax (though I'm not fundamentally opposed either). But, otherwise, we seem to be...
Very interesting, thanks @g5becks!
> we can safely say that `await record` will effectively pointwisely await _every component_ of the record, and evaluate to the result of awaiting a `Future
Barring that, you could do something fairly nice with extensions: ```dart extension FutureRecord2Extension on (Future, Future) { Future wait() async { var (f1, f2) = this; var [e1 as T1,...
Closing this as a duplicate of #2321 since that has covers the same territory and has more details.