Roland Tepp

or do you mean the other way around — that would be `Date.string`, I guess...

Well, the trouble here is that all those `*.string` methods are currently returning similarly formatted output across the board. Date.string returns `yyyy-mm-dd`, Time.string returns `hh:mm:ss`, DateTime.string returns `Date.string + 'T'...

On the other hand, the YYMMDD and HHmmss formats are also valid ISO representations. so it would be relatively easy to change default output to the shorter variant. I personally...

I somewhat agree on the point of defining equality contracts for `Date`/`Time`/`DateTime`/`ZoneDateTime` equality. The only question here is, should we define the contract on the level of `Date` interface or...

Okay. makes sense.

@jvasileff, @DiegoCoronel the equality of `TimeZone` has not really been tackled yet. The thing is that we have two types of time zones in `ceylon.time`: - _Fixed offset time zones_...

@DiegoCoronel I can't really remember the reasoning for defining the units of time and date as interfaces. For what it's worth, it seems to me that the equality should be...

Time zone adds a semantic detail to the instant, that could be important to the application. Otherwise why use `ZoneDateTime` instead of `Instant`?

So, this is library developer ease of use versus end-user ease of use question. The way I see this. `ceylon.html` biggest strength so far is that it is a fairly...

I think it was a conscious decision at the time not to normalize `equals()` -- the reasoning at the time was that `equals()` is (and `hash`) are very likely to...