Duration constructor args should be reversed

[DartBot]

This issue was originally filed by @seaneagan

---

The most commonly used time unit for Durations is milliseconds. Generally, the most commonly used arguments should come first, so you can avoid having to refer to the argument by name, especially when the name is really long as with "milliseconds":

const Duration(milliseconds: 500)

Thus, I think it would be better if the Duration constructor arguments were reversed:

const Duration([int milliseconds, int seconds, int minutes, int hours, int days]);

so that now I can just do:

const Duration(500)

This would also leave the door open to adding larger time units to Duration in the correct order in the future (issue #1426):

const Duration([int milliseconds, int seconds, int minutes, int hours, int days, int weeks, int months, int years]);

[anders-sandholm]

cc @floitschG.
Removed Type-Defect label.
Added Type-Enhancement, Area-Library, Triaged labels.

[floitschG]

Probably not the direction you wanted it to go, but this is not an issue anymore: The duration class uses named arguments, and therefore requires them to be written out.

Wrt the argument that this allows adding larger time units: this would have actually been an argument against changing the order. We are much less likely to add larger time units than smaller units (for example "microseconds").
The reason for not adding bigger units, is that they depend on the date and the timezone where they are in. This means that duration.inSeconds would need to know where and when it was.

---

Added AssumedStale label.