Rachel Brindle

poke @diniska, it's been more than 3 months.

@jessesquires I agree with you on shipping Quick v6 and Nimble v11 together. That makes a lot of sense.

@tomerhouzz I'm (slowly) working on this. It's not my highest priority, but I do want to see this get in. There are issues with [my current approach](https://github.com/Quick/Quick/pull/1160) that I haven't...

This would be helpful with the async stuff I'm doing. It might even make sense to to make async support require this and leave the existing API as-is. I like...

> This will make the syntax much lighter, but it'll probably break the Xcode integrations like gutter icons. This is my main concern with removing too much of the boilerplate....

I spent some time this weekend working with this. I can see eventually deprecating the current way of building tests in favor of using ResultBuilder. Especially once we remove the...

Hey @JosephDuffy! Really sorry about this delay. Is this still an issue you're seeing with current versions of Xcode?

Hey @GLinnik21! Thanks for the issue! We'll take care of this and make sure we support Objective-C on the Swift Packages release in the next version of Nimble. For now,...

This is definitely something we should fix as soon as we can. Ultimately, my investigation was able to trace it down to an issue with CwlPreconditionTesting, and they already have...

I'm going to bump this to the v11 milestone. If there's a fix released for this upstream, we'll issue a bugfix release of Nimble including that fix.