Clarify localtime and oldtime's docs #626
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In response to #578, there really isn't anything Chrono can do to actually prevent the invalid
memory accesses in libc -- all we can do is tell people not to set env vars. In my experience and
from conversations surrounding this issue, setting env vars is rare and definitely just shouldn't
be done once the process has more than one thread running. Hopefully isn't an an awful burden on
users, either in terms of feature reduction or of security scanning.