Skip to content

Add DST ambiguity note to TzSpecificLocalTimeToSystemTime(Ex) documentation #2065

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

Open
wants to merge 2 commits into
base: docs
Choose a base branch
from

Conversation

rkg96
Copy link

@rkg96 rkg96 commented Aug 4, 2025

This PR updates the Remarks section of the TzSpecificLocalTimeToSystemTime and TzSpecificLocalTimeToSystemTimeEx APIs documentation to clarify behavior around Daylight Saving Time (DST) transitions.

Specifically, it adds a note explaining that:

  • Certain local times near DST transitions may be ambiguous (e.g., repeated during fall back) or invalid (e.g., skipped during spring forward).
  • The API may not return the "correct" UTC value in these cases due to the lack of a DST indicator in the SYSTEMTIME structure.
  • Developers should be aware of this limitation and consider alternative approaches for time-sensitive operations.

This clarification is based on MSFT-internal bug reports and developer feedback and aims to prevent confusion and misinterpretation of API behavior during DST transitions.

rkg96 added 2 commits August 4, 2025 12:29
This PR updates the Remarks section of the TzSpecificLocalTimeToSystemTime API documentation to clarify behavior around Daylight Saving Time (DST) transitions.

Specifically, it adds a note explaining that:

Certain local times near DST transitions may be ambiguous (e.g., repeated during fall back) or invalid (e.g., skipped during spring forward).
The API may not return the "correct" UTC value in these cases due to the lack of a DST indicator in the SYSTEMTIME structure.
Developers should be aware of this limitation and consider alternative approaches for time-sensitive operations.
This clarification is based on internal bug reports and developer feedback, and aims to prevent confusion and misinterpretation of API behavior during DST transitions.

✅ Motivation:
Improve developer understanding of edge cases in time conversion.
Reduce misuses and incorrect assumptions about API behavior near DST boundaries.
Align documentation with observed behavior and internal guidance.
@rkg96
Copy link
Author

rkg96 commented Aug 4, 2025

@microsoft-github-policy-service agree company="Microsoft"

Copy link

@rkg96 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants