Skip to content
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

Library + Main Class name clash #90

Closed
DevAgani opened this issue May 17, 2023 · 1 comment
Closed

Library + Main Class name clash #90

DevAgani opened this issue May 17, 2023 · 1 comment

Comments

@DevAgani
Copy link

~/ios/Pods/IOSSecuritySuite/IOSSecuritySuite/IOSSecuritySuite.swift:14:14: Public class 'IOSSecuritySuite.IOSSecuritySuite' shadows module 'IOSSecuritySuite', which may cause failures when importing 'IOSSecuritySuite' or its clients in some configurations; please rename either the class 'IOSSecuritySuite.IOSSecuritySuite' or the module 'IOSSecuritySuite', or see swiftlang/swift#56573 for workarounds

Version: 1.9.7

@r3ggi
Copy link
Collaborator

r3ggi commented May 17, 2023

Hey,

Thanks for raising this issue. The library name AFAIK doesn't violate Swift naming module & class naming convention and the problem you mention is a bug in the Swift compiler.

The bug reporter claims that the bug itself is rather rare:

This problem is usually invisible until a client tries to read the module interface, which is rarely done in normal development workflows, so the invalid module interface may not be noticed until much later.

For ISS I don't see it breaks any functionality, so let's keep this library as it is.

@r3ggi r3ggi closed this as completed May 17, 2023
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 a pull request may close this issue.

2 participants