Skip to content

[ClangImporter] Test for not being in a module correctly. #9992

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

jrose-apple
Copy link
Contributor

For the Optional<Module *> returned by getClangSubmoduleForDecl, the outside Optional specifies whether there's an answer at all. That answer can still be null if the declaration comes from a bridging header. In this particular case, we're guaranteed to get an answer, but that answer may be null.

rdar://problem/32463543

For the Optional<Module *> returned by getClangSubmoduleForDecl, the
outside Optional specifies whether there's an answer at all. That
answer can still be null if the declaration comes from a bridging
header.  In this particular case, we're guaranteed to get an answer,
but that answer may be null.

rdar://problem/32463543
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

@jrose-apple
Copy link
Contributor Author

By the way, this only happens in Swift 4 mode.

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 76e64a9
Test requested by - @jrose-apple

@jrose-apple
Copy link
Contributor Author

@swift-ci Please test macOS

@jrose-apple jrose-apple merged commit fbf5a51 into swiftlang:master May 31, 2017
@jrose-apple jrose-apple deleted the null-is-not-none-part-5723 branch May 31, 2017 16:24
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