-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Emit Debug Variables for Errors Bound in Catch Clauses #40372
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
5ef33f6
to
1bbf2aa
Compare
@swift-ci 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.
Oh, this is great, thanks!
@kastiglione does this take care of all known remaining issues with error variables? |
Much appreciated! It looks to cover all the cases. |
After this is committed, I can add some lldb level tests. |
do { | ||
try throwing() | ||
} | ||
catch let error as MyError, let error as MyError { |
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'm curious why multiple/duplicate bindings isn't an error.
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.
Absolutely agreed https://bugs.swift.org/browse/SR-15548
1bbf2aa
to
017f133
Compare
@swift-ci test windows platform |
Build failed |
@swift-ci smoke test Linux platform |
Build failed |
Make error variables accessible to a fresh debug scope for the catch clause. rdar://85982381
017f133
to
b2619ef
Compare
@swift-ci smoke test |
Neat ⛵ |
This was merged with a regression on the Windows bot that is indicated in the CI results on the PR: https://ci-external.swift.org/job/swift-PR-windows/18932/consoleText |
Make error variables accessible to a fresh debug scope for the catch clause.
rdar://85982381