| Age | Commit message (Collapse) | Author |
|---|
|
Apple dropped support for some older platforms, so we can also remove
the annotations for them.
See https://developer.apple.com/support/xcode/ for the supported
versions.
|
|
This is a follow-up to #89178. This updates the `<__config_site>`
macros.
|
|
We waited before supporting std::jthread fully because we wanted to
investigate other implementation strategies (in particular one involving
std::mutex). Since then, we did some benchmarking and decided that we
wouldn't be moving forward with std::mutex. Hence, there is no real
reason to punt on making std::jthread & friends non-experimental.
|
|
In essence, this header has always been related to configuration of
the library but we didn't want to put it inside <__config> due to
complexity reasons. Now that we have sub-headers in <__config>, we
can move <__availability> to it and stop including it everywhere since
we already obtain the required macros via <__config>.
|
|
that take `stop_token`
- This is section 32.6.4 of P0660R10
- https://eel.is/c++draft/thread.condvarany.intwait
Differential Revision: https://reviews.llvm.org/D153441
|
|
There are discussions about different ways of implementing `stop_token` to make it more performant
mark `stop_token` as experimental to allow us to change the design before it is shipped
Co-authored-by: Louis Dionne <ldionne.2@gmail.com>
Differential Revision: https://reviews.llvm.org/D154700
|
|
Implement stop_token
http://eel.is/c++draft/thread.stoptoken
|
