Andrew Chang

The only workaround I’ve found is to call `stop()` twice on the current `XCTestRun`. This causes an assertion failure within `xctest` that stops the current test from executing further, but...

> I am guessing is it tied to the fact that the test is not using a host application. Right, extensions themselves [require a host app to run](https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/ExtensionOverview.html#//apple_ref/doc/uid/TP40014214-CH2-SW2) so you...

I think it’s definitely worth looking into. I’m prioritizing some big changes to the framework and generator for 0.18, so if you have the bandwidth it would help tremendously. Note...

Thanks for reporting. Unfortunately I wasn’t able to repro this crash (see the changes under Examples/CocoaPodsExample): https://github.com/andrewchang-bird/mockingbird/tree/repro-issue-276 Could you provide additional context or a minimal repro project for this?

A workaround for the `producesBadCode` issue (missing inferred generic type specialization) is to keep the member declarations the same (referencing the inherited generic types) and use generic type constraints instead....

I have a pending branch that adds Linux compatibility for the generator here: https://github.com/birdrides/mockingbird/tree/dev/andrewchang-bird/add-linux-compat Right now it’s only tested on CentOS 8 but it’ll likely work for all distros. The...

It’s possible to install Mockingbird onto the generated Pods project (you’ll need to do it as a post `pod install`action). I’ll look into improving the docs around this, but the...

We distribute the `_InternalSwiftSyntaxParser` library with the binary because SwiftSyntax has strict version requirements. For example, SwiftSyntax for Swift 5.4 cannot be load the parser from the Swift 5.5 toolchain...

Would need to know the package manager you’re using. But the error means that there’s something misconfigured such that the framework isn’t linked to your test target.

Thanks for flagging, Saman. Although not ideal, one workaround is to use compilation directives to gate an available and unavailable variant of the method. ```swift class Foo { #if TEST...