Skip to content

[sil-parser] Fix harmless bug when parsing ossa. #26851

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

gottesmm
Copy link
Contributor

Specifically, we were preferring the always correct ownership kind specified by
the FunctionType and ignoring what we parsed from the argument. This PR changes
ossa to give a nice error when this is detected and fixes the places where this
tests were written incorrectly.

@gottesmm gottesmm requested a review from jckarter August 26, 2019 21:05
@gottesmm
Copy link
Contributor Author

@jckarter This is the reason why you weren't getting the ownership error when miswriting that test in the ossa PR.

Specifically, we were preferring the always correct ownership kind specified by
the FunctionType and ignoring what we parsed from the argument. This PR changes
ossa to give a nice error when this is detected and fixes the places where this
tests were written incorrectly.
@gottesmm gottesmm force-pushed the pr-47fb2b3ffcc142eb6fe2703fdcbe61f25c7af463 branch from 0ae75b1 to af565e7 Compare August 27, 2019 17:18
@gottesmm
Copy link
Contributor Author

@swift-ci test and merge

4 similar comments
@gottesmm
Copy link
Contributor Author

@swift-ci test and merge

@gottesmm
Copy link
Contributor Author

@swift-ci test and merge

@gottesmm
Copy link
Contributor Author

@swift-ci test and merge

@gottesmm
Copy link
Contributor Author

@swift-ci test and merge

@swift-ci swift-ci merged commit 94112ef into swiftlang:master Aug 27, 2019
@gottesmm gottesmm deleted the pr-47fb2b3ffcc142eb6fe2703fdcbe61f25c7af463 branch August 27, 2019 20:56
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