-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
approximate time formatting? #4
Comments
Currently, you can do that by truncating the value. I.e. to skip fracional seconds, use:
To show days:
In this scenario, an application chooses the granularity, though. And I don't think there is one size fits all approach for that. I.e. one app may show just the number of days when the duration is > 24 hours, and the other could print "1day 8h" up to 5 days. Currently, the priority of the library is being extremely stable, as it's used in env_logger which is used for every other rust program. So I don't think we can afford to add such functionality since I expect it to be backed in multiple iterations. However, we may add one eventually. What do you think? |
If I have to do the truncation myself then humantime isn't gaining my anything. That's fine, it's just a few lines of code that I have copied from c++ project to project for years. I just thought I'd mention it as a useful human friendly time feature missing from the library. |
Yes, it's easy as long as you solving a very specific problem. And much harder when you're trying to make a library suitable for a lot of users with different use cases. So closing this for now. |
A relatively simple method that allows specifying the maximum amount of units would be very handy. Eg 1 would mean only the largest unit ( |
Well that's interesting. But different kinds of rounding might also be needed for this case. |
@tailhook
and it produces: Who to blame? :) |
Filled a bug: rust-lang/rust#90225 |
Yes, that's a duration constructor error, not formatting issue. |
When I saw the title "humantime", I thought I'd have something that I could use to give a friendly output of how long my program has run (i.e. when it's been running for 36 days, I don't care about picoseconds).
Would adding that as a feature be of interest?
The text was updated successfully, but these errors were encountered: