-
Notifications
You must be signed in to change notification settings - Fork 21
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
Drop chrono, use std Time #7
Comments
I have no real opinion on this. What are the problems with chrono, exactly? And is std::time powerful enough that we can get away with using just std::time? |
My main issue with chrono is it's golden cage, there are issues open since a longer time regarding conversion from chrono time to the std time etc. It's brilliant in parsing etc, but can be a real pain if you have to get out of the normal chrono universe. So: I'm biased. |
I'm closing this as chrono seems to do it's job and I'm against changing one of the essential input/ouput types of a working library if there's no hard fact why this would be required. |
It would be best to drop chrono and use std time, as chrono has some serious problems regarding conversion etc, you're kind of locked into the chrono universe as it is now.
The text was updated successfully, but these errors were encountered: