cut catch-all exceptionStr overload

Summary: There are no correct uses of the catch-all overload of `folly::exceptionStr`. Every use is a bug of some kind, leading to the impression that this overload ought to be removed.

Differential Revision: D26539622

fbshipit-source-id: dc2ca0781ea02f1327a334bb1fe2e533fa46d1b3
This commit is contained in:
Yedidya Feldblum 2021-02-26 12:17:05 -08:00 committed by Facebook GitHub Bot
parent 31b5ed02fd
commit 355f92564a

View File

@ -534,9 +534,7 @@ folly::Future<bool> FileInode::isSameAsSlow(
return getSha1(fetchContext)
.thenTry([expectedBlobSha1](folly::Try<Hash>&& try_) {
if (try_.hasException()) {
XLOG(DBG2) << "Assuming changed: "
<< folly::exceptionStr(
try_.tryGetExceptionObject<std::exception>());
XLOG(DBG2) << "Assuming changed: " << try_.exception();
return false;
} else {
return try_.value() == expectedBlobSha1;
@ -584,9 +582,7 @@ folly::Future<bool> FileInode::isSameAs(
return folly::collectUnsafe(f1, f2).thenTry(
[](folly::Try<std::tuple<Hash, Hash>>&& try_) {
if (try_.hasException()) {
XLOG(DBG2) << "Assuming changed: "
<< folly::exceptionStr(
try_.tryGetExceptionObject<std::exception>());
XLOG(DBG2) << "Assuming changed: " << try_.exception();
return false;
} else {
auto hashes = std::move(try_).value();