Excessive using statements in Sort.jl

[LilithHafner]

This smells bad:

import ..@__MODULE__, ..parentmodule
const Base = parentmodule(@__MODULE__)
using .Base.Order
using .Base: copymutable, LinearIndices, length, (:), iterate, elsize,
    eachindex, axes, first, last, similar, zip, OrdinalRange, firstindex, lastindex,
    AbstractVector, @inbounds, AbstractRange, @eval, @inline, Vector, @noinline,
    AbstractMatrix, AbstractUnitRange, isless, identity, eltype, >, <, <=, >=, |, +, -, *, !,
    extrema, sub_with_overflow, add_with_overflow, oneunit, div, getindex, setindex!,
    length, resize!, fill, Missing, require_one_based_indexing, keytype, UnitRange,
    min, max, reinterpret, signed, unsigned, Signed, Unsigned, typemin, xor, Type, BitSigned

using .Base: >>>, !==

There are two many symbols to read.
What's special about >>> and !==?
length is listed twice.
Are all these really used? Probably not.
Roughly all but 4 of these 62 symbols are imported automatical by using Base

[N5N3]

But Core.Compiler exports none of them?

[LilithHafner]

I don't think Core.Compiler exports any of them, because when I type using Core.Compiler and then try first I don't get "WARNING: both Core.Compiler and Base export "first"; uses of it in module Main must be qualified"

[LilithHafner]

I think we are in agreement, I edited my reply to try to clarify that.

[N5N3]

Opps, my fault.

But Core.Compiler exports none of them?

What I mean is

julia> Core.Compiler.Sort.Base
Core.Compiler

julia> Base.Sort.Base
Base

And the long list above seems unavoidable? (Of course we can remove repetitive/unnecessary using )

[LilithHafner]

And the long list above seems unavoidable?

I'm also not sure how to avoid it

Of course we can remove repetitive/unnecessary using

I slip that into #45222

[JeffBezanson]

Yes, this weirdness is due to Sort being included in both Base and Core.Compiler. We might be able to remove all or most of it in the future with better separate compilation support. Removing the duplicates is of course welcome. Other than that I will close this since it's not a significant problem and it will be a while before we can really address it.