Make most arguments to Date constructor optional.

corelib/src/date.dart

Index: corelib/src/date.dart
diff --git a/corelib/src/date.dart b/corelib/src/date.dart
index c7b5668baaf6ece57186d95a9a5fe01576f26644..5bbfb1d21d368d49fc4ce0ff27e86cf6ae765a69 100644
--- a/corelib/src/date.dart
+++ b/corelib/src/date.dart
@@ -36,13 +36,15 @@ interface Date extends Comparable, Hashable default DateImplementation {
    * Constructs a [Date] instance based on the individual parts, in the
    * local time-zone.
    */
+  // TODO(floitsch): the spec allows default values in interfaces, but our
+  // our tools don't yet. Eventually we want to have default values here.

[ngeoffray, 2012/05/15 12:17:35]

our our -> our

[floitsch, 2012/05/15 12:34:22]

Done.

   Date(int year,
-       int month,

[sorinmocanu, 2012/05/15 12:21:59]

Where will you document the possible combinations of arguments which are
possible?
Crazy example, should a date implementation support year + hours?

[floitsch, 2012/05/15 12:34:22]

Each argument has a default value. 1 for month and day, and 0 for the others.
Each can be passed as named argument without affecting the others.
So yes: new Date(2012, milliseconds: 499) is legal (although probably not very
common).

-       int day,
-       int hours,
-       int minutes,
-       int seconds,
-       int milliseconds);
+       [int month,
+        int day,
+        int hours,
+        int minutes,
+        int seconds,
+        int milliseconds]);
 
   /**
    * Constructs a [Date] instance based on the individual parts.