Skip to content

Remove __consuming from Code Completion #17096

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
merged 1 commit into from
Jun 10, 2018

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented Jun 10, 2018

Set the UserInaccessible bit and remove __consuming from code
completion until we commit to a real keyword.

rdar://40828289

Set the UserInaccessible bit to remove __consuming from code
completion until we commit to a real keyword.

rdar://40828289
@CodaFi CodaFi force-pushed the all-consuming-fire branch from 89464fa to df698d2 Compare June 10, 2018 22:06
@CodaFi
Copy link
Contributor Author

CodaFi commented Jun 10, 2018

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit 60f2002 into swiftlang:master Jun 10, 2018
@CodaFi CodaFi deleted the all-consuming-fire branch June 10, 2018 22:42
// FIXME: __consuming should not appear in CodeCompletion until it is
// finalized in a language proposal.
if (Name == "__consuming")
return;
Copy link
Contributor

@benlangmuir benlangmuir Jun 11, 2018

Choose a reason for hiding this comment

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

We should form the DeclAttributeKind and use DeclAttribute::isUserInaccessible() instead of handling __consuming explicitly. I thought we already did that, but it looks like we only handle it on attribute completion right now.

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