diff options
author | Ahmad Samir <[email protected]> | 2024-09-02 22:42:10 +0300 |
---|---|---|
committer | Marc Mutz <[email protected]> | 2024-09-03 14:42:24 +0000 |
commit | 051488c5faf5410e938978d4c1609c7a85074c57 (patch) | |
tree | 924ce9afe25aa010a02c7a629da001e297189f1e /src/plugins/platforms/wasm/qwasmwindow.cpp | |
parent | 2ef1a338a91659871675514921f9a7dc8d1c8805 (diff) |
QTimer: fix calculation error in API docs
The range guaranteed by std¹ for nanosecond resolution is ±292 years,
not ±292 million.
¹ https://eel.is/c++draft/time.syn,
https://en.cppreference.com/w/cpp/chrono/duration#Helper_types,
std::cout << chrono::floor<years>(nanoseconds::max()) << '\n';
Since, in general, there is no integer type with ≥ 45 bits, but < 64
bits, the practical limit for milliseconds remains, indeed, ±292
million, so the QDateTime docs don't need fixing.
Pick-to: 6.8
Change-Id: I5ae7f9706f147c6f490ba17b10cebe96426bbba2
Reviewed-by: Marc Mutz <[email protected]>
Diffstat (limited to 'src/plugins/platforms/wasm/qwasmwindow.cpp')
0 files changed, 0 insertions, 0 deletions