Conversation
|
I agree this makes more sense and will make the inspect output easier to read. I plan to merge this before 2.7 is released unless there are objections. |
|
I object this change. If you want to introduce such Web friendly date library, don't build it on top of current date library. |
|
@nurse I can revert this, however, first please consider that "inspect should suggest its internal" is no longer a reason to do so. The date library since 1.9.3 does not store the julian day number for dates in the typical case where it is initialized via |
|
@jeremyevans The fact it doesn't calculate julian day number is implementation detail. I think Date#inspect should show the difference between |
|
@nurse OK. I'll revert this change. |
|
Revert committed at 875d563. |
I'd like to raise a discussion on the following change:
Justification: for most of contexts where
Datecould be used (web apps, data conversion scripts, experiments and so on), the "((2455200j,0s,0n),+0s,2299161j)" suffix is meaningless, and just obscures the data reading. Imagine the (pretty simple) example:Whether it is a list of dates we extract from DB, or have in test (of some scheduling library), or parse from CSV, I believe the "before" example is very hard to read and provides no additional value.
On the other hand, for the rare contexts when values like "julian day number" matter, the
((2458697j,0s,0n),+0s,2299161j)format seem to be too terse to be easily used by anybody not 200% familiar with library's internals.