Erik Ernst
Erik Ernst
But I had less detail. ;-)
These topics have been mentioned several times above, but let me refer to the latest comments: @lrhn wrote: > Adding `covariant` might be reasonable. Probably not necessary for structs. Right,...
> I don't think I'd want them in the primary constructor. Which is the reason why I suggested that they would be > (in the class body) and not in...
@lrhn, would you be able to take a look at this PR? I'm removing @leafpetersen as a reviewer, because it's obviously a good idea to broaden this effort a bit.
@lrhn, when you're back from vacation, could you take a look at this one?
Interesting! This proposal is somewhat similar to the super-parameter feature which was added to Dart in 2.17. It may be confusing to use the same keyword, but here's a look...
One more thing needs to be handled: We currently rely on mixins to give rise to an implicitly induced class. This class must contain a set of members which is...
July 11th: Added some extra `\commentary{..}` where the text seemed to need it.
> The spec does say: > >> Dart source text is represented as a sequence of Unicode code points. Right, and that's actually a subtle statement because it restricts the...
I'd emphasize purpose 2 and 3: The language specification (plus any temporary feature specifications) should specify the language for developers, such that they can construct Dart programs with whatever behavior...