Source: dart.dev/resources/la...

New language spec in revision draft (link might break, but in case anyone cares that *technically* that’s for old dart- at time of writing, it still applies):
storage.googleapis.com/dart-specifi...

(5) Simple syntax solution: make “inherited” a keyword ONLY when in front of “static” so you’d get “inherited static” and could then do the exact same syntax as any other instance member function - including just the signature to leave the definition up to the implementers.

(4) It is an incredibly stupid limitation that holds the language back. And to hide behind “well it’s confusing” - if true: dogwater reason. Normalize difficult things (especially when they’re not even hard). If untrue: just come out and say “it’s hard to support, we didn’t want to” 🤡

(3) At best, you can manually define the constructor on each subclass, then add the class manually to some sort of deserializer on the base class. But that is prone to errors unless you use code-gen, and even if you do that, the type checker won’t understand what you’re doing, as T != BaseClass.

(2) The obvious use-case for this is data models for serializable data, and therefore the base class will require all subclasses to define static constructor/factory methods for the creation of an instance member.

That use case is presently not possible in Dart.

Mission Accomplished 😴👍

That's not to say it's impossible to rise above a Tuesday, more that on Tuesdays: it's all on you to supply your own positivity 😂

I get a great kick out of the deluge of "Fuck Tuesday" snaps I get every week. Maybe it'll be a thing on here too... Here's to hoping! 😅

Looking forward to these making a difference ✊