Ben Hamilton (Ben Gertzfield)

I did some investigation into the ins and outs of using the swift and clang command-line to compile binaries which use Swift and Objective-C together. Here's what I found: https://www.facebook.com/beng/posts/10153662256352720...

I hacked together very very basic Swift support for Xcode project generation: https://github.com/facebook/buck/tree/swift I updated the demo app to use it: https://github.com/fbsamples/bucksamples/tree/swift This doesn't support Swift frameworks yet, but the...

Sorry for the long silence here. Expect to see some movement soon!

So the very basics have landed. You can build `apple_binary()` rules and `apple_bundle()` rules with one or more `swift_library()` dependencies. OS X, iOS simulator, and iOS device are all working....

I just learned about `valueless_by_exception`: https://en.cppreference.com/w/cpp/utility/variant/valueless_by_exception so I assume this logic is to implicitly deal with that case — if so, we can close this issue.

If it is possible to detect that these two cases from the spec are `noexcept` for all the types in the `variant` (maybe using the `noexcept()` operator — this would...

Could we only do this optimization when exceptions are disabled? On Tue, Feb 16, 2021, 10:30 Fabio wrote: > I believe the problem lies in the fact that any type...

I mean, if -fno-exceptions is set in the compilation unit which #includes variant.hpp, it's not possible for variant.hpp to *throw* the bad_variant_access() exception, right? But it still tries to do...

I guess what I'm saying is, if I know in my particular environment that it's not possible for the variant to be valueless, I expect an exhaustive std::visit to be...

Huh! I just noticed that somewhere between clang 8 and clang 9, the std::variant implementation got a whole lot more optimized, and it somehow elides all the logic for std::bad_variant_access,...