LWG3316: Correctly define epoch for utc_clock / utc_timepoint #100428

Activity

1. cjdb

   added

   good first issuehttps://github.com/llvm/llvm-project/contributehttps://github.com/llvm/llvm-project/contribute

   libc++libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.

   c++20

   chronoIssues related to std::chronoIssues related to std::chrono

   lwg-issueCanonical version of a Library Working Group issue.Canonical version of a Library Working Group issue.

   on Jul 24, 2024
2. llvmbot commented on Jul 24, 2024

   

   llvmbot

   on Jul 24, 2024

   Member

   More actions

   Hi!

   This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

   1. Check that no other contributor has already been assigned to this issue. If you believe that no one is actually working on it despite an assignment, ping the person. After one week without a response, the assignee may be changed.
   2. In the comments of this issue, request for it to be assigned to you, or just create a pull request after following the steps below. Mention this issue in the description of the pull request.
   3. Fix the issue locally.
   4. Run the test suite locally. Remember that the subdirectories under test/ create fine-grained testing targets, so you can e.g. use make check-clang-ast to only run Clang's AST tests.
   5. Create a Git commit.
   6. Run git clang-format HEAD~1 to format your changes.
   7. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation. Mention this issue in the description of the pull request.

   If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.
3. llvmbot commented on Jul 24, 2024

   

   llvmbot

   on Jul 24, 2024

   Member

   More actions

   @llvm/issue-subscribers-good-first-issue

   Author: Christopher Di Bella (cjdb)

   Details

   **Link:** https://wg21.link/lwg3316

   This appears to be an editorial clarification.
4. llvmbot commented on Jul 24, 2024

   

   llvmbot

   on Jul 24, 2024

   Member

   More actions

   @llvm/issue-subscribers-c-20

   Author: Christopher Di Bella (cjdb)

   Details

   **Link:** https://wg21.link/lwg3316

   This appears to be an editorial clarification.
5. cjdb

   changed the title [-]Confirm 'LWG3316 Correctly define epoch for `utc_clock` / `utc_timepoint`' should be marked as 'Nothing to do' in the status page[/-] [+]Confirm 'LWG3316 Correctly define epoch for `utc_clock` / `utc_timepoint`' is a no-op[/+] on Jul 26, 2024
6. ldionne

   added this to libc++ Standards Conformanceon Jul 30, 2024
7. cjdb

   added

   potentially good for outreachConsider this issue as a good first issue for someone that has spoken to an experienced LLVM devConsider this issue as a good first issue for someone that has spoken to an experienced LLVM dev

   and removed

   good first issuehttps://github.com/llvm/llvm-project/contributehttps://github.com/llvm/llvm-project/contribute

   on Aug 1, 2024
8. ldionne

   changed the title [-]Confirm 'LWG3316 Correctly define epoch for `utc_clock` / `utc_timepoint`' is a no-op[/-] [+]LWG3316: Correctly define epoch for `utc_clock` / `utc_timepoint`[/+] on Aug 1, 2024
9. ldionne

   moved this to Todo in libc++ Standards Conformanceon Aug 21, 2024