-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support for timestamps #70
Conversation
P0355 has not been implemented entirely by The plan is vendor parts of |
96f0ef8
to
2c321b6
Compare
Signed-off-by: Julien Jerphanion <[email protected]>
Signed-off-by: Julien Jerphanion <[email protected]> Co-authored-by: Klaim <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need additional tests to check compilation since all_base_types_t
is already instantiated in the metaprogramming tests.
Signed-off-by: Julien Jerphanion <[email protected]> Co-authored-by: Johan Mabille <[email protected]>
Signed-off-by: Julien Jerphanion <[email protected]>
Signed-off-by: Julien Jerphanion <[email protected]>
8f358a5
to
05adbcc
Compare
For reference, feature testing macros aren't present in stdlibc++ 12 and 13. I have not checked for stdlibc++14 yet, but we can't expect to use it, I believe. |
include/sparrow/data_type.hpp
Outdated
#include <version> | ||
#include <chrono> | ||
|
||
#if __cpp_lib_chrono > 201907L |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
__cpp_lib_chrono
(like any other FTM) might not be implemented in compiler, and it thus unusable.
See the discussions in llvm/llvm-project#73953.
As discussed, let's use |
Signed-off-by: Julien Jerphanion <[email protected]>
c1d5493
to
1d515c3
Compare
I iterated on the PR
I removed the mingw tests because
On a separate note, a difference between the polyfill and std::chrono is that the literals in the polyfill are prefixed with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, Sylvain. I just have one suggestion before merging this PR.
For the readers' information, those issues are worth reading and watching:
.github/workflows/windows.yml
Outdated
- {compiler: default} | ||
- {compiler: msvc} | ||
- {compiler: clang} | ||
- {compiler: msvc, date-polyfill: 'ON' } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, I am subscribed to GitHub Action Runners' new releases.
- {compiler: msvc, date-polyfill: 'ON' } | |
# TODO: Reintroduce default (or just mingw) when the new version is release | |
# See: https://github.com/actions/runner-images/commits/main/images/windows/Windows2022-Readme.md | |
# See: https://www.mingw-w64.org/changelog/ | |
- {compiler: msvc, date-polyfill: 'ON' } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest we explicitely invoke mingw rather than calling it because it is the default toolchain with Ninja.
Co-authored-by: Alexis Placet <[email protected]> Signed-off-by: Julien Jerphanion <[email protected]>
Co-authored-by: Alexis Placet <[email protected]> Signed-off-by: Julien Jerphanion <[email protected]>
This version or a newer on is expected by the Visual Studio2022. See: https://github.com/xtensor-stack/sparrow/actions/runs/9381890699/job/25832125441?pr=70 Signed-off-by: Julien Jerphanion <[email protected]>
Fix #52.