Skip to content

Naming conflicts (due to public extensions) #32

@d4rkd3v1l

Description

@d4rkd3v1l

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 ;-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions