<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in __mutex_base</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4887d047 - [libc++][NFC] Replace enable_if with __enable_if_t in a few places</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#4887d047</link>
        <description>[libc++][NFC] Replace enable_if with __enable_if_t in a few placesReviewed By: ldionne, #libcSpies: jloser, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D128400

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Sun, 03 Jul 2022 23:21:44 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>368faaca - [libc++] Revert &quot;Protect users from relying on detail headers&quot; &amp; related changes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#368faaca</link>
        <description>[libc++] Revert &quot;Protect users from relying on detail headers&quot; &amp; related changesThis commit reverts 5aaefa51 (and also partly 7f285f48e77 and b6d75682f9,which were related to the original commit). As landed, 5aaefa51 hadunintended consequences on some downstream bots and didn&apos;t have propercoverage upstream due to a few subtle things. Implementing this issomething we should do in libc++, however we&apos;ll first need to addressa few issues listed in https://reviews.llvm.org/D106124#3349710.Differential Revision: https://reviews.llvm.org/D120683

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Mon, 28 Feb 2022 21:37:25 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>5aaefa51 - [libcxx][modules] protects users from relying on detail headers</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#5aaefa51</link>
        <description>[libcxx][modules] protects users from relying on detail headerslibc++ has started splicing standard library headers into much morefine-grained content for maintainability. It&apos;s very likely that outdatedand naive tooling (some of which is outside of LLVM&apos;s scope) willsuggest users include things such as &lt;__ranges/access.h&gt; instead of&lt;ranges&gt;, and Hyrum&apos;s law suggests that users will eventually begin torely on this without the help of tooling. As such, this commitintends to protect users from themselves, by making it a hard error foranyone outside of the standard library to include libc++ detail headers.Differential Revision: https://reviews.llvm.org/D106124

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Fri, 25 Feb 2022 18:59:32 +0000</pubDate>
        <dc:creator>Christopher Di Bella &lt;cjdb@google.com&gt;</dc:creator>
    </item>
<item>
        <title>489637e6 - [libc++] Granularize chrono includes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#489637e6</link>
        <description>[libc++] Granularize chrono includesReviewed By: Quuxplusone, #libcSpies: libcxx-commitsDifferential Revision: https://reviews.llvm.org/D120141

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 23 Feb 2022 22:05:22 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>fa6b9e40 - [libc++] Normalize all our &apos;#pragma GCC system_header&apos;, and regression-test.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#fa6b9e40</link>
        <description>[libc++] Normalize all our &apos;#pragma GCC system_header&apos;, and regression-test.Now we&apos;ll notice if a header forgets to include this magic phrase.Differential Revision: https://reviews.llvm.org/D118800

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 02 Feb 2022 01:16:40 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>5726e559 - [libc++] Modularize &lt;chrono&gt;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#5726e559</link>
        <description>[libc++] Modularize &lt;chrono&gt;I didn&apos;t split the calendar bits more than this because there was littlebenefit to doing it, and I know our calendar support is incomplete.Whoever picks up the missing calendar bits can organize these headersat their leisure.Differential Revision: https://reviews.llvm.org/D116965

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Mon, 10 Jan 2022 19:56:43 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>feb80aa9 - [libc++] `= delete` member functions with // = delete;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#feb80aa9</link>
        <description>[libc++] `= delete` member functions with // = delete;Use `= delete` for member functions that are marked with `// = delete;`Reviewed By: ldionne, Quuxplusone, #libcSpies: jloser, libcxx-commitsDifferential Revision: https://reviews.llvm.org/D115291

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 08 Dec 2021 09:57:12 +0000</pubDate>
        <dc:creator>Nikolas Klauser &lt;nikolasklauser@berlin.de&gt;</dc:creator>
    </item>
<item>
        <title>cb793e1a - [libc++][NFCI] Remove uses of _LIBCPP_INLINE_VAR</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#cb793e1a</link>
        <description>[libc++][NFCI] Remove uses of _LIBCPP_INLINE_VARAll supported compilers provide support for inline variables in C++17 now.Also, as a fly-by fix, replace some uses of _LIBCPP_CONSTEXPR by justconstexpr.The only exception in this patch is `std::ignore`, which is providedprior to C++17. Since it is defined in an anonymous namespace, it alwayshas internal linkage anyway, so using an inline variable there doesn&apos;tprovide any benefit. Instead, `inline` was removed entirely on `std::ignore`.Differential Revision: https://reviews.llvm.org/D110243

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 22 Sep 2021 13:35:32 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d7d70601 - Eliminate _LIBCPP_EQUAL_DELETE in favor of `=delete`.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#d7d70601</link>
        <description>Eliminate _LIBCPP_EQUAL_DELETE in favor of `=delete`.All supported compilers have supported `=delete` as an extensionin C++03 mode for many years at this point.Differential Revision: https://reviews.llvm.org/D109942

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Fri, 17 Sep 2021 02:47:36 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>317e92a3 - [libc++] Enable `explicit` conversion operators, even in C++03 mode.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#317e92a3</link>
        <description>[libc++] Enable `explicit` conversion operators, even in C++03 mode.C++03 didn&apos;t support `explicit` conversion operators;but Clang&apos;s C++03 mode does, as an extension, so we can use it.This lets us make the conversion explicit in `std::function` (even in &apos;03),and remove some silly metaprogramming in `std::basic_ios`.Drive-by improvements to the tests for these operators, in additionto making sure all these tests also run in `c++03` mode.Differential Revision: https://reviews.llvm.org/D104682

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Tue, 15 Jun 2021 16:57:54 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>bfbd73f8 - [libc++] Alphabetize and include-what-you-use. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#bfbd73f8</link>
        <description>[libc++] Alphabetize and include-what-you-use. NFCI.Differential Revision: https://reviews.llvm.org/D102781

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 19 May 2021 15:57:04 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>4cd6ca10 - [libc++] NFC: Normalize `#endif //` comment indentation</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#4cd6ca10</link>
        <description>[libc++] NFC: Normalize `#endif //` comment indentation

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Tue, 20 Apr 2021 16:03:32 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne.2@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>781c476c - [libc++] ADL-proof vector&lt;bool&gt; by adding _VSTD:: qualification on calls.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#781c476c</link>
        <description>[libc++] ADL-proof vector&lt;bool&gt; by adding _VSTD:: qualification on calls.This affects only vectors with weird/malicious allocators,the same corner case covered in D91708, but for `vector&lt;bool&gt;` this time.Also ADL-proof &lt;__tree&gt;, which affects only sets and maps with weird/maliciousallocators where the ADL trap is in the *fancy pointer type*.Also drive-by _VSTD:: qualification in the guts of std::bind,std::packaged_task, std::condition_variable.Differential Revision: https://reviews.llvm.org/D93424

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 16 Dec 2020 00:32:29 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d586f92c - [libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#d586f92c</link>
        <description>[libc++] Consistently replace `std::` qualification with `_VSTD::` or nothing. NFCI.I used a lot of `git grep` to find places where `std::` was being usedoutside of comments and assert-messages. There were three outcomes:- Qualified function calls, e.g. `std::move` becomes `_VSTD::move`.    This is the most common case.- Typenames that don&apos;t need qualification, e.g. `std::allocator` becomes `allocator`.    Leaving these as `_VSTD::allocator` would also be fine, but I decided    that removing the qualification is more consistent with existing practice.- Names that specifically need un-versioned `std::` qualification,    or that I wasn&apos;t sure about. For example, I didn&apos;t touch any code in    &lt;atomic&gt;, &lt;math.h&gt;, &lt;new&gt;, or any ext/ or experimental/ headers;    and I didn&apos;t touch any instances of `std::type_info`.In some deduction guides, we were accidentally using `class Alloc = typename std::allocator&lt;T&gt;`,despite `std::allocator&lt;T&gt;`&apos;s type-ness not being template-dependent.Because `std::allocator` is a qualified name, this did parse as we intended;but what we meant was simply `class Alloc = allocator&lt;T&gt;`.Differential Revision: https://reviews.llvm.org/D92250

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Fri, 27 Nov 2020 16:02:06 +0000</pubDate>
        <dc:creator>Arthur O&apos;Dwyer &lt;arthur.j.odwyer@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>12805513 - [libc++] Remove some workarounds for C++03</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#12805513</link>
        <description>[libc++] Remove some workarounds for C++03We don&apos;t support any compiler that doesn&apos;t support variadics and rvaluereferences in C++03 mode, so these workarounds can be dropped. There&apos;sstill *a lot* of cruft related to these workarounds, but I try to tacklea bit of it here and there.

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Fri, 09 Oct 2020 16:33:49 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>fda3825c - [libc++] Ensure __config always defines certain configuration macros.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#fda3825c</link>
        <description>[libc++] Ensure __config always defines certain configuration macros.

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Fri, 13 Dec 2019 20:42:07 +0000</pubDate>
        <dc:creator>Eric Fiselier &lt;eric@efcs.ca&gt;</dc:creator>
    </item>
<item>
        <title>e16f2cb6 - [libc++] Take 2: Implement LWG 2510</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#e16f2cb6</link>
        <description>[libc++] Take 2: Implement LWG 2510Summary:LWG2510 makes tag types like allocator_arg_t explicitly defaultconstructible instead of implicitly default constructible. It alsomakes the constructors for std::pair and std::tuple conditionallyexplicit based on the explicit-ness of the default constructibilityfor the pair/tuple&apos;s elements.This was previously committed as r372777 and reverted in r372832 due tothe commit breaking LLVM&apos;s build in C++14 mode. This issue has now beenaddressed.Reviewers: mclow.listsSubscribers: christof, jkorous, dexonsmith, libcxx-commitsTags: #libcDifferential Revision: https://reviews.llvm.org/D65161llvm-svn: 372983

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Thu, 26 Sep 2019 14:51:10 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>a3d337a9 - Revert r372777: [libc++] Implement LWG 2510 and its follow-ups</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#a3d337a9</link>
        <description>Revert r372777: [libc++] Implement LWG 2510 and its follow-upsThis also reverts: - r372778: [libc++] Implement LWG 3158 - r372782: [libc++] Try fixing tests that fail on GCC 5 and older - r372787: Purge mentions of GCC 4 from the test suiteReason: the change breaks compilation of LLVM with libc++, for details seehttp://lists.llvm.org/pipermail/libcxx-dev/2019-September/000599.htmlllvm-svn: 372832

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 25 Sep 2019 09:10:38 +0000</pubDate>
        <dc:creator>Ilya Biryukov &lt;ibiryukov@google.com&gt;</dc:creator>
    </item>
<item>
        <title>95411dd4 - [libc++] Implement LWG 2510</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#95411dd4</link>
        <description>[libc++] Implement LWG 2510Summary:LWG2510 makes tag types like allocator_arg_t explicitly defaultconstructible instead of implicitly default constructible. It alsomakes the constructors for std::pair and std::tuple conditionallyexplicit based on the explicit-ness of the default constructibilityfor the pair/tuple&apos;s elements.Reviewers: mclow.lists, EricWFSubscribers: christof, jkorous, dexonsmith, libcxx-commitsTags: #libcDifferential Revision: https://reviews.llvm.org/D65161llvm-svn: 372777

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Tue, 24 Sep 2019 20:18:54 +0000</pubDate>
        <dc:creator>Louis Dionne &lt;ldionne@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>85e26f56 - Revert &quot;Revert &quot;Implement std::condition_variable via pthread_cond_clockwait() where available&quot;&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/include/__mutex_base#85e26f56</link>
        <description>Revert &quot;Revert &quot;Implement std::condition_variable via pthread_cond_clockwait() where available&quot;&quot;With the fix for non-Linux.This reverts commit c1c519d2f1a66dd2eeaa4c321d8d7b50f623eb71.llvm-svn: 372242

            List of files:
            /llvm-project-15.0.7/libcxx/include/__mutex_base</description>
        <pubDate>Wed, 18 Sep 2019 18:13:32 +0000</pubDate>
        <dc:creator>Dan Albert &lt;danalbert@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
