Skip to content

Always diagnose request evaluator cycles #24213

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 4 commits into from
Apr 23, 2019

Conversation

slavapestov
Copy link
Contributor

Turns out only minor fixes were needed, so let's enable this and make sure we don't regress.

NFC for now, but this problem causes some tests to fail once we
enable cycle diagnostics.
If there are no braces, the start and end location of the range is
the same token. When performing a lookup at this token's location,
don't consider it to be "inside" the braces.

NFC for now, but this problem causes some tests to fail once we
enable cycle diagnostics.
@slavapestov slavapestov requested a review from xymus April 23, 2019 01:53
@swift-ci

This comment has been minimized.

@swift-ci

This comment has been minimized.

@swift-ci

This comment has been minimized.

If there are no braces, the start and end location of the range is
the same token, so don't create a TypeOrExtensionBody scope at all.

NFC for now, but this problem causes some tests to fail once we
enable cycle diagnostics.
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@swift-ci

This comment has been minimized.

@swift-ci

This comment has been minimized.

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

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.

Very excited for this!

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

@slavapestov slavapestov merged commit e303cea into swiftlang:master Apr 23, 2019
@@ -1886,8 +1890,7 @@ bool swift::fixDeclarationObjCName(InFlightDiagnostic &diag, ValueDecl *decl,
return false;
}

// Determine the Objective-C name of the declaration.
ObjCSelector name = *decl->getObjCRuntimeName();
auto name = *nameOpt;
auto targetName = *targetNameOpt;
Copy link
Contributor

Choose a reason for hiding this comment

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

I was a little confused by these two lines when I read them. I guess the idea is that these should only be None when the declaration is implicit or a subscript? If so, maybe there should be a comment here or a sentence in the doc comment to that effect.

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