You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don’t think so. Old versions of Swift had issues with return values and closures. I think there just needs to be a test / verification that something like this works:
it(“should work”) {
expect { try someFunc() }.toNot(throwError()).to(equal(5))
}
The swift compiler couldn’t figure out that `it` only accepted `Void` as a return value and incorrectly inferred the closure to have a return value. I’m pretty sure that has been fixed in recent Swift versions.
- Jeff
On Dec 22, 2016, 2:52 PM -0800, Yurii Samsoniuk ***@***.***>, wrote:
Since the Expectation is an immutable structure, is there any reason why we cannot just extend its methods with an additional result returning self?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
From: Quick/Quick#432
It would seem to be useful to be able to generate two tests by eg:
This form doesn't work, I don't see any docs about how to achieve the same thing, or is there some reason that eludes me that this isn't a good idea?
The text was updated successfully, but these errors were encountered: