Tony Allevato

You can try `--strategy=SwiftCompile=sandboxed` to force it to use the sandbox, to see if that prints out any messages about the sandbox not being enabled somehow. ...which makes me wonder...

There don't appear to be any major fundamental issues preventing `libdispatch` from being statically linked, it's just not there yet. So having this functionality will be good for when that...

That isn't really a supported use of the `includes` attribute (or `textual_hdrs`) on `objc_library`; it just works by accident for Objective-C because header maps use the same command line flag...

Your use case makes sense, but rather than just add another key to `SwiftInfo`, this got me thinking about a better way to refine the providers as a whole. One...

Yeah, my build log shows `-num-threads 36` when I do a standard release build. I attempted to de-parallelize a debug build as much as possible to do a comparison, and...

The closest thing to this is Bazel's [`--test_filter` command line flag](https://docs.bazel.build/versions/0.28.0/command-line-reference.html#flag--test_filter), but I believe it would be the responsibility of each test runner implementation to honor that setting and pass...