fbshipit-source-id: 4f62ac9b038b4836187c96faf3b8ab88ee34c0b2

fbshipit-source-id: a77fcf5804e47df856faff006577f3a5847917c8

fbshipit-source-id: 7a4d2e9c7fff8248faddaa5b3c246eb66782c97e

fbshipit-source-id: 2fdd9fd6788874a0bb0ecc54d67856cd7a5666f1

fbshipit-source-id: 741a3452b94feb7837733ffadc677a4cd96c3271

fbshipit-source-id: 87c80e673533d18b0b99ffc673eff466204af9d9

fbshipit-source-id: 18530764c159a753f3e2abdb36648ee0f6ca46fb

fbshipit-source-id: d46faae4572b04c4352b79b18c647a0bce689a66

fbshipit-source-id: ecedf66e7d6e1ea6bcbe1ba68091f6ffdf62c260

fbshipit-source-id: 0901852e14521df7f5f8ed6ce338cbc9cfceb279

fbshipit-source-id: e4951d42e306b7af6ae595394a3994d6e4235083

fbshipit-source-id: 8e93ce30fd17d832bcc09ae3ea5e4cf6cbd887b2

fbshipit-source-id: bfecdc1c0e934cf073e610c2cb98518bfde84ecd

fbshipit-source-id: 0af2aa0b3cc551bbfef396ca0a7ad6975caa8279

fbshipit-source-id: 1df9cc44331327b62fb7e20f22f8f512fe4e6ecd

fbshipit-source-id: 0e4317ea86a60c50408cf415972bd048596ac0b2

fbshipit-source-id: 2363aa0c02923504fcc36d927604a27a2f0558ba

fbshipit-source-id: 4eeda45c9b4bb8256f71c9e644cd70f83b539fd0

fbshipit-source-id: 07e042879b008fbd34f583ae4351459bd5ae84a9

fbshipit-source-id: 30a9f3571fb0a26d0023e3596105d2a38cf2d5e1

fbshipit-source-id: f5fba149a4200b522bf90700f320685cbf0737f9

Summary:
[Folly] Pure C++ for TSAN annotation wrappers, v.s. using the preprocessor.

The implementation uses the preprocessor in order to support platforms without weak symbols, but the interface is now pure C++.

Reviewed By: nbronson

Differential Revision: D10291176

fbshipit-source-id: 3636652793b8d0da59c7c9b1095d4c1b0c506372

Summary:
This setting is already set by FollyConfigChecks.cmake, but was not
actually defined by folly-config.h

This setting is only checked by a few of the concurrency tests.

Reviewed By: igorsugak

Differential Revision: D10405959

fbshipit-source-id: 1602730e6adb7e05a82e65bdc5c367d105f59224

Summary:
When using clang with libstdc++ `-latomic` must be explicitly specified
as part of the link command in order to get some of the symbols required
for C++ std::atomic support.

The old autoconf-based build did have this check (added in github commit
60a5636b, D2519083).  However this check was missing from the
CMake-based build.

Reviewed By: igorsugak

Differential Revision: D10405960

fbshipit-source-id: 37291edc5a387e2e966ece79241aa00312194cbd

Summary: Folly zerocopy improvements

Reviewed By: djwatson

Differential Revision: D10324653

fbshipit-source-id: dacb2941e08eaf2e7588c04a01800e297a0643cf

Summary: Update the CMake files to support compiling with ASAN.

Reviewed By: igorsugak

Differential Revision: D10401270

fbshipit-source-id: 08c7fe3b661c17ba21fd8a8eb3b5cf716ebd3d35

Summary: then to thenValue to remove calls to deprecated functions.

Reviewed By: yfeldblum

Differential Revision: D10366311

fbshipit-source-id: 99c4cd8bcfa2d9db80c2d8eb22300d92609a36fc

Summary:
Add a new macro to track if folly was compiled with ASAN enabled.  This
is in addition to the existing FOLLY_SANITIZE_ADDRESS macro, which
reports if the current .cpp file is being compiled with ASAN enabled.

In particular, these macros differ in open source builds if folly was
compiled without ASAN enabled, but some of its headers are being
included from downstream libraries that are being built with ASAN
enabled.

Previously several headers would define structures differently based on
`FOLLY_SANITIZE_ADDRESS`, which meant that different .cpp files would see
different definitions of these structures.  `FOLLY_ASAN_ENABLED` is generally
the correct macro to use for situations like this.

This diff fixes F14Table.h to use FOLLY_ASAN_ENABLED, but several other
headers probably should also be updated in the future.

I did not change the behavior of FOLLY_SANITIZE_ADDRESS, since it appears to
be used by several projects outside of folly, and they expect it to report if
their code is being compiled with ASAN enabled.

At the moment the open source build does not support compiling with ASAN,
so FOLLY_ASAN_ENABLED is always disabled in open source builds.

Reviewed By: nbronson

Differential Revision: D10401271

fbshipit-source-id: 7e028737b42eecae93f06538dcf76dd64bd32e6a

Summary: FOLLY_HAVE_LIBJEMALLOC does not get defined, breaking builds in certain configurations (e.g., jemalloc present, Fedora 28 with cmake). FOLLY_USE_JEMALLOC does. Substitute former with latter,

Differential Revision: D10349332

fbshipit-source-id: e30245f8f19c6b2b7861cd88a4e1719a15c10fce

Summary: [Folly] Use explicit memory orders in `SerialExecutor`.

Reviewed By: andriigrynenko

Differential Revision: D10370862

fbshipit-source-id: 5cc5903d188b131f851a62690cd182de6ba47eb9

Summary:
Reduced contention with removing connection between queue_ and schedule_ access.
Replaced std::queue with unbounded multiple producer single consumer queue.

Reviewed By: yfeldblum

Differential Revision: D10345872

fbshipit-source-id: 3307d908d6e4826eab4d981447c8771021bfe580

Summary: Pends the freeing of the internal SSL until the socket is finally destroyed. This ensures that the async job can write out the result and call the socket's callback. This also always calls restartSSLAccept in order to let it handle errors and cleaning up of async jobs.

Reviewed By: knekritz

Differential Revision: D9599917

fbshipit-source-id: 8c4ce8b762fe59f08c2a40e76a0bebe59cd2929e

Summary: Allows for a runner to execute the accept function and return the result via a callback. If no runner is specified, it simply does the accept as usual.

Reviewed By: yfeldblum

Differential Revision: D9849138

fbshipit-source-id: ef43ccc8668bcf1fe7f75b0b6fdcdba7adc891da

Summary:
Fixes #947.

>libc++ 6+ (and Xcode 10's libc++, which seems to be based on it) adds std::launder, but does not define the __cpp_lib_launder feature-test macro. As a result, folly's lang/Launder.h concludes std::launder is missing and defines its own implementation. Since std::launder does actually exist, ADL causes 'ambiguous call' errors whenever a standard library type like std::pair is laundered within the folly namespace. (This breaks compilation of folly's futures, for example, and I believe it will cause compilation issues anywhere else F14Map is used, since it launders std::pair in its F14Policy.)
Pull Request resolved: https://github.com/facebook/folly/pull/948

Reviewed By: ot

Differential Revision: D10287027

Pulled By: yfeldblum

fbshipit-source-id: be3469fe6855d2af266e1b6a62968770e8cfd76f

Summary: [Folly] Opportunity to use `exchange` in `ScopeGuardImpl`.

Reviewed By: Orvid

Differential Revision: D10119838

fbshipit-source-id: 64a00f4f60d913f8af248ebf891f730d2c69fec8

Summary: then to thenValue to remove calls to deprecated functions.

Reviewed By: Orvid

Differential Revision: D10362133

fbshipit-source-id: e638d24e95c5c6c46d0366eabcd1ff9537421bc6

Summary:
Just require that MSVC is at least MSVC 2017

Closes: https://github.com/facebook/folly/issues/949

Reviewed By: yfeldblum

Differential Revision: D10355264

fbshipit-source-id: 52ac7489200285f06c5f4fb3d176f6427974b163

Summary:
Make StringPiece and MutableStringPiece implicitly convertible
to std::string_view.  This diff also adds FOLLY_HAS_STRING_VIEW to
Portability.h, which will be defined to be 0 or 1.

Reviewed By: vitaut

Differential Revision: D10187660

fbshipit-source-id: 90e6f3ac82e47eae423dab8f1de1d39e5ac997c4

Summary: [Folly] `exchange` in `DelayedDestruction` move-ctor.

Reviewed By: knekritz

Differential Revision: D10320776

fbshipit-source-id: b6b1f910b927098e61f6f6c8e414fdfcca843033

Summary: Clear the zerocopy maps in AsyncSocket::failAllWrites if the fd_ has been closed

Reviewed By: djwatson

Differential Revision: D10347608

fbshipit-source-id: a60d0450b13d4989d6849ca4cbe1057ecb6b92dd