Skip to content

Conversation

@harlanhaskins
Copy link
Contributor

In #30614, we started consuming XRefNonLoadedModuleErrors while loading
conformances, since a conformance to a type we cannot load usually
indicates we're trying to load a protocol that was declared in an
@_implementationOnly imported module.

We should also consume TypeErrors that we see where the underlying reason
is an XRefNonLoadedModuleError, since they're likely indicators of the
same thing.

In swiftlang#30614, we started consuming XRefNonLoadedModuleErrors while loading
conformances, since a conformance to a type we cannot load usually
indicates we're trying to load a protocol that was declared in an
@_implementationOnly imported module.

We should also consume TypeErrors that we see where the underlying reason
is an XRefNonLoadedModuleError, since they're likely indicators of the
same thing.
@harlanhaskins harlanhaskins requested a review from xymus August 3, 2020 23:23
@harlanhaskins
Copy link
Contributor Author

@swift-ci please test

Copy link
Contributor

@xymus xymus left a comment

Choose a reason for hiding this comment

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

That makes a lot of sense. Thank you!

@swift-ci
Copy link
Contributor

swift-ci commented Aug 4, 2020

Build failed
Swift Test Linux Platform
Git Sha - 50aa603

@harlanhaskins
Copy link
Contributor Author

LLDB test timed out...

@swift-ci please test Linux

@harlanhaskins
Copy link
Contributor Author

@swift-ci please test Linux

@harlanhaskins harlanhaskins merged commit d67d7eb into swiftlang:master Aug 4, 2020
static llvm::Error consumeErrorIfXRefNonLoadedModule(llvm::Error &&error) {
// Missing module errors are most likely caused by an
// implementation-only import hiding types and decls.
// rdar://problem/60291019
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's okay to add a radar number into the commit message, but in the code they are not useful to any Swift developers outside of Apple. I would just try to say as much as possible about the problem in the comment itself (which you already did!) and move the radar link into a footnote in the git commit message.

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