A modern programming language that makes developers happier.

kotlinlang

I'm modelling notification objects. The "default" ones, with name, description and so on, and then I have "progress" notifications which have everything contained in the "default" ones + a field for a message when the process is complete

Isn’t that the definition of a class and a subclass ?

You’d have a class for a Notification which may be a progress one or not, and a subclass ProgressNotification which overrides the right things

yeah... I just was wondering if there was a way to reduce verbosity, because subclass needs to declare all the constructor arguments in its constructor and pass them to super class. But I guess this is unavoidable