You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to parallel-haskell
I am working with Control.Distributed.Process.Platform.Time and came across timeToMs.
I am accustomed to ms being milliseconds, and us being microseconds (according to SI units), camel-cased.
Is this an appropriate name for the function?
Alan
Tim Watson
unread,
Apr 22, 2013, 5:41:51 AM4/22/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AlanKim Zimmerman, parallel-haskell
Hi Alan,
On 22 April 2013 10:02, AlanKim Zimmerman <alan...@gmail.com> wrote:
I am accustomed to ms being milliseconds, and us being microseconds (according to SI units), camel-cased.
Is this an appropriate name for the function?
No you're quite right, it should be timeToUs - when I first wrote that function I didn't realise that System.Timeout was using microseconds and subsequently noticed when I saw various tests failing - see commit 85f3c4d. Actually I'm quite tempted to change it to `timeToMicros` instead, just to make absolutely sure there's no confusion. Either way, I'll make sure this is changed before the next/first release to hackage.
Thanks very much for pointing this out anyway. I'd completely forgotten about the naming inconsistency - doing too many concurrent tasks! ;)