You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-cpp
The hard part is understanding your domain well enough to know which tool is right for the job.problem here is not with chrono, but general understanding of how timezones work and how to design approach, I'd suggest to move to softwareengineering.stackexchange.com<chrono>which in turn has overturned the dogma stated in the question. The dogma is likely still good advice if you're not programming in C++. Try this in C and the compiler will not help you correct minor type-o's and think-o's. And if you happen to get it right, the code will be far less maintainable. It will be hard to read, and the type system won't help you detect minor mistakes in future maintenance.java.time(2014) have the same concepts (local/zoned/etc) in their design, type safety, but none of them (including your example with chrono) are error resistant, they do no help correct minor typos/thinkos, like if you forget to useget_sys_time, I'd also challengedogmastatement, while I can imagine that some people could say that, it is nowhere near "dogma", utc is great for exact points in time (like past ornow), but "everyday 7:00" is not point in time, so you just cannot use utc for this, you have to "generate local time", and then use it one way or another