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

Naming conflicts (due to public extensions) #32

Open
d4rkd3v1l opened this issue Feb 7, 2018 · 0 comments
Open

Naming conflicts (due to public extensions) #32

d4rkd3v1l opened this issue Feb 7, 2018 · 0 comments

Comments

@d4rkd3v1l
Copy link

I know this may be not the right place for this. So I'm sorry for posting this here, but don't know were else I should put this.

In a pod I'm using, there is a CGFloat+Extensions.swift which I think comes from somewhere here (at least from RW, as it has your Razeware header comment in it).
My problem is that, because those extensions are public, I get naming conflicts e.g. when using them in multiple modules (pods, or even my own).
So I was just wondering, why you declared them public, and don't just stick to the internal default? This is really annoying :-/ Or am I seeing this wrong?
Anyway as these Extensions are just copied around, there is probably no way to stop this ;-)

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

No branches or pull requests

1 participant