Bob Nystrom
Bob Nystrom
Perhaps we could do what Slava suggests without needing special language support by: 1. Define a couple of macros in the core library like `@equatable`, etc. Those macros add an...
Yeah, I'm with Lasse. I agree that giving users a choice to make is a bad thing, but I think being able to document positional fields by name is really...
> Do we actually have to support getters? Maybe we could limit ourselves to destructurring only "primitive" properties: meaning it _must_ to be a field. We could, but I think...
> I'd like to make sure that the stable getters feature is understood the way it was intended, so I have to add some comments to this characterization. I hope...
> Another thing we can't do with extensions is to introduce constructors of the target class (I forgot to mention constructors in the first version of the proposal in several...
> I'd personally rather move towards allowing any statement inside a collection, and use `yield` to emit values. Probably going to be a hard sell. For what it's worth, when...
For what it's worth, you could also do: ```dart final canRunWithSoundNullSafety = await _allMigratedToNullSafety(packageGraph, reader, () sync* { yield* orderedBuilders.map((b) => b.import); yield* postProcessBuilderDefinitions.map((b) => b.import); }()); ``` I agree...
> Just to throw out a crazy idea. Is there any chance that static metaprogramming #1482 could be applied to collection literals? I don't think this is a crazy idea....
I *suspect* that we won't want to allow these to be torn off. It might work in all circumstances, but I would be surprised if we didn't run into corners...
> there isn't anything special about those functions that I can think of? They are definitely kind of special when it comes to generative constructors. Whether other ones are special......