Actions
Improvements #14680
openWDate::toTimePoint is not able to represent all dates.
Start date:
07/20/2026
Due date:
% Done:
0%
Estimated time:
Description
Since std::chrono::system_clock::time_point cannot represent all of the dates WDate can represent, we may get an incorrect date when storing a WDate object in a database, or when using WDateTime . This is does however only impacts dates that are several centuries in the past or in in the future. Making this unlikely to impact most use-cases.
Updated by Romain Mardulyn 23 days ago
- Status changed from New to InProgress
- Assignee set to Romain Mardulyn
Updated by Romain Mardulyn 16 days ago
- Status changed from New to InProgress
- Assignee set to Romain Mardulyn
Updated by Romain Mardulyn 15 days ago
- Status changed from InProgress to New
- Assignee deleted (
Romain Mardulyn) - Target version changed from 4.14.1 to future
Actions