<div dir="ltr">Does this mean that date->seconds always returns inexacts now? Or does it return inexacts only when it wouldn't be an integer?<div><br></div><div>(I'm not excited about either possibility but the second seems bad only if you consider TR.)<br> <div><div><br>Robby</div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 1, 2013 at 5:22 PM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">At Wed, 30 Jan 2013 22:23:04 -0500, Asumu Takikawa wrote:<br> > On 2013-01-30 23:20:45 +0100, Pierpaolo Bernardi wrote:<br> > > Any reason not to define current-date in this way? there's a nanosecond<br> > > field there wanting to get into action.<br> ><br> > While we're on the subject, it's also weird that `date->seconds` has a<br> > contract accepting date? and so doesn't handle date*'s extra nanosecond<br> > field (note that `seconds->date` produces date*s):<br> ><br> > Welcome to Racket v5.3.2.3.<br> > -> (require racket/date)<br> > -> (define s (* #i1/1000 (current-inexact-milliseconds)))<br> > -> s<br> > 1359602380.5059009<br> > -> (date->seconds (seconds->date s))<br> > 1359602380<br> <br> </div>I've changed `current-date'.<br> <br> Some existing code may rely on `date->seconds' returning an exact<br> integer, so I've added `date*->seconds'.<br> <div class="HOEnZb"><div class="h5"><br> _________________________<br> Racket Developers list:<br> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br> </div></div></blockquote></div><br></div>