Add note about supported windows versions to <chrono>#3906
Merged
jborsecnik merged 1 commit intoMicrosoftDocs:mainfrom May 20, 2022
barcharcraz:chrono_windows_version
Merged
Add note about supported windows versions to <chrono>#3906jborsecnik merged 1 commit intoMicrosoftDocs:mainfrom barcharcraz:chrono_windows_version
jborsecnik merged 1 commit intoMicrosoftDocs:mainfrom
barcharcraz:chrono_windows_version
Conversation
Contributor
|
@barcharcraz : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #label:"aq-pr-triaged" |
Collaborator
|
#sign-off |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
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.
Some features of chrono are not supported when running on older versions of windows, but that's only documented in our github changelogs and is very, very easy to miss.
This clarifies the situation directly in the toplevel chrono documentation.
It may also be good to add a note or link back from the individual time-zone functions.