Remi Rousselet

> * Augmentation libraries (yet another library type) would not be needed. We already have parts, library files, libraries, and potentially macro libraries, adding augmentation libraries might be nice for...

> However, adjacent strings are prone to subtle errors. Consider: > > ```dart > var fruits = [ > 'apple', > 'banana' > 'cherry', > 'date' > ]; > ```...

Would syntax sugar over callable classes works? Right now we can achieve the equivalent of named constructors for functions using callable classes: ```dart const someFunction = _SomeFunction(); class _SomeFunction {...

I definitely agree that union types expressed as `A | B | C` instead of something like sealed classes are a better IMO. Technically speaking, sealed classes don't bring any...

@werediver > Every concrete sealed class [in Kotlin] is a subclass of a particular base class. From the docs: That's the problem. There's no common subclass with the different values...

About the generated copyWith, will it support `struct.copyWith(property: null)`?

Nice! I saw that line but wasn't sure about the implications I suppose two remaining useful "functions" would be a fromJson/toJson. But I suppose we're unlikely to get those?

Would static function composition be in the scope of this feature? At the moment, higher-order functions in Dart are fairly limited since they require knowing the full prototype of the...

> It cannot change the signature of the function, but it can access arguments But an important part of function composition is also the ability to inject parameters and ask...

> I don't think that is prohibitive though as long as you are allowed to generate a new function/method next to the existing one with the signature you want That's...