Skip to content

[4.0] Sema: Ensure the array type for variadic tuple shuffles is always set. #10428

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

Merged

Conversation

jckarter
Copy link
Contributor

@jckarter jckarter commented Jun 20, 2017

Explanation: We neglected to set up the type of the variadic argument array when invoking a variadic subscript with a single argument.

Scope: Source compatibility regression affecting vapor

Issue: SR-5264 | rdar://problem/32860988

Risk: Low, small bug fix.

Testing: Swift CI, compatibility test suite

We neglected to set it on one path (a scalar-to-tuple conversion path currently only taken by subscript applications). Change TupleShuffleExpr's constructor to take it as an argument so this mistake is harder to make in the future. Fixes SR-5264 | rdar://problem/32860988.
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@jckarter
Copy link
Contributor Author

@swift-ci Please test source compatibility

@jckarter jckarter requested a review from DougGregor June 20, 2017 23:49
@jckarter
Copy link
Contributor Author

@DougGregor Mind reviewing this for 4.0?

@jckarter jckarter changed the title Sema: Ensure the array type for variadic tuple shuffles is always set. [4.0] Sema: Ensure the array type for variadic tuple shuffles is always set. Jun 20, 2017
Copy link
Member

@DougGregor DougGregor left a comment

Choose a reason for hiding this comment

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

LGTM!

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - e19cefa
Test requested by - @jckarter

@jckarter
Copy link
Contributor Author

@swift-ci Please test OS X

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.

4 participants