Skip to content

[Parser] Fix-it for declaration attributes being applied to parameter types (SR-215) #1197

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

SquaredTiki
Copy link
Contributor

Original PR #673 but reverted due to test failures and later due to typo. Third time's a charm, eh? CI should spot anything now which is a neat addition. Original description:

As described in SR-215, previously the fix-it was suggesting that declaration attributes applied to parameter types be moved to before the function func declaration itself.

This pull request fixes this so that it is instead moved to before the parameter name.

@slavapestov
Copy link
Contributor

@swift-ci Please test

@slavapestov
Copy link
Contributor

This looks good at first glance -- do you mind squashing the two commits together? Also it looks like the commit message on the first one is wrong (it's not really fixing a typo -- it's implementing the whole change)

@SquaredTiki
Copy link
Contributor Author

@slavapestov I've squashed them all together now and fixed a build failure noticed by the CI.

@slavapestov
Copy link
Contributor

@swift-ci Please test

@slavapestov slavapestov self-assigned this Feb 20, 2016
@CodaFi
Copy link
Contributor

CodaFi commented Jul 7, 2016

@SquaredTiki Do you feel this diagnostic is still relevant to Swift 3?

@SquaredTiki
Copy link
Contributor Author

@CodaFi I don't believe so as @noescape is now meant to be applied to parameter types as can be seen here. Hence I shall close this PR.

@SquaredTiki SquaredTiki closed this Jul 9, 2016
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.

3 participants