-
Notifications
You must be signed in to change notification settings - Fork 10.5k
SILGen: Fix for 'try?' leaking the error value #1740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci Please fix |
|
||
enum Markings { case Tuxedo, Tortoise } | ||
|
||
class Cat : Equatable { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like cats, but StdlibUnittest provides LifetimeTracked
type for leak checking. And the harness automatically checks that LifetimeTracked.instances == 0
at the end of every test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! And I'm glad we both agree on the cat part too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tortoise == naughty.
@swift-ci Please test |
If only this worked... |
dad0052
to
ddeaecd
Compare
@swift-ci Please test |
The error is passed in to the catch block as a +1 value but we were just dropping it on the floor. Fixes https://bugs.swift.org/browse/SR-972
ddeaecd
to
cfb5c66
Compare
@swift-ci Please test |
I'm guessing this won't make it into Xcode 7.3 GM…? |
May I suggest this one being cherry-picked for the (potential) 2.2.1 release? It'll have big impact in our production code. Thanks for your consideration 🙇. |
No description provided.