Skip to content

qualify uses of Not #83

Open
Open
@bgctw

Description

@bgctw

When importing both SimpleTraits and DataFrames, I do not figure out how to deal with
"both DataFrames and SimpleTraits export "Not"; uses of it in module TwPrototypes must be qualified"

Specifically, SimpleTraits somehow inlines unqualified usages of Not somewhere in the code, which I do not know how to transform to qualified, which causes compiler errors "UndefVarError: Not not defined" -> with stack traces leading into SimpleTraits source code.
e.g.
@ ~/scratch/twutz/julia_cluster_depots/packages/SimpleTraits/l1ZsK/src/SimpleTraits.jl:171 [inlined]

I suggest as a first measure to replace "Not" by "SimpleTraits.Not" in all the code of SimpleTraits.

Is it possible to not export Not from SimpleTraits? Would this break too much depending code - which would need to adapt and qualify their usages of Not?
Personally, I did not use Not explicitly yet (but obviously implicitly via macro) in my code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions