Is the "required" keyword really necessary with non nullable types?

[LasseRosenow]

if we have a method that has parameters with labels, by default they would be optional, so if they are not specified when the method is called, they would be null.

To also have parameters with labels that are not optional there is the required keyword.

But since non nullability is a thing in dart, a labeled parameter needs to either be nullable without a required keyword or be non nullable and have the required keyword.

But if a parameter is non nullable it is theoretically implicitly required so having the required keyword seems to be very unnecessary In my opinion. And I think the language would be much cleaner without it.

Code example for required labeled parameters:

// Current required
void foo({required String bar});

// Proposed required
void foo({String bar});

// Optional stays the same:
void foo({String? bar});

[LasseRosenow]

Closing this as it's a duplicate of #878