Bug 6724 – core.time.dur should use SI symbols for durations, not the ad hoc contractions it uses now

Status
RESOLVED
Resolution
WONTFIX
Severity
enhancement
Priority
P2
Component
druntime
Product
D
Version
D2
Platform
Other
OS
Linux
Creation time
2011-09-24T14:11:00Z
Last change time
2016-10-15T01:01:42Z
Assigned to
nobody
Creator
siegelords_abode

Comments

Comment #0 by siegelords_abode — 2011-09-24T14:11:17Z
That is: ms,ns,s,h,d,µs (I'd accept us as an alternative) If not, at the very least use 'secs' and not 'seconds' so it matches the sub-second interval names.
Comment #1 by issues.dlang — 2011-09-24T14:42:11Z
All units seconds and greater are spelled out completely. All sub-second units are abbreviated. That's by design. We _could_ make it so that there are multiple names for each unit type, but then that gets messy - both in terms of code and in terms of people having to decipher template constraints. It's just cleaner to accept one specific string for each unit type. So, I think that having multiple is ultimately a bad idea. Changing the unit strings would break code for little gain IMHO. And going for names as short as you suggest is error-prone. It's already bad enough that msecs, usecs, and hnsecs are as similar as they are. The functions that the unit strings are used with are exactly the kind of functions where it's often easy to not notice a bug when the units are slightly off. So, making them even less distinct would _not_ be a good idea as far as I'm concerned.