Skip to content

Call closures passed as @autoclosure explicitly. #237

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

Closed
wants to merge 1 commit into from

Conversation

tkremenek
Copy link
Member

Needed for Swift 5 migration.

Copy link
Contributor

@briancroom briancroom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this will need to be adjusted such that we're not losing the benefits of lazily evaluating the message closures only when an assertion failure is detected.

@tkremenek
Copy link
Member Author

Thanks @briancroom. After I started building with this patch I started seeing these problems. I'll tinker and adjust to match the original semantics.

@tkremenek
Copy link
Member Author

I realized these changes make no sense. I'm going to go back and re-analyze why I saw the errors I did.

@tkremenek tkremenek closed this Nov 16, 2018
@tkremenek
Copy link
Member Author

I think the errors I was seeing was due to regressions in the compiler due to the handling of @autoclosure. I should have examined them more closely before creating this PR.

@tkremenek tkremenek deleted the swift5-migration branch November 16, 2018 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants