JuliaLang / julia / #38007

20%

Build Type

push

local

Committed by web-flow

Commit Message

Only implicitly `using` Base, not Core (#57357)

Inspired by the question in
https://github.com/JuliaLang/julia/pull/57311#issuecomment-2648144227, I
want to revisit the basic setup where every module `using`s both `Core`
and `Base`. In general, I think we mostly expect users to inferface with
`Base`, not `Core`, so this PR changes things to only have new modules
`using` Base (while re-exporting all `Core` names from `Base`). There
should be little user-visible impact from these changes. The only
situation I can think of where it makes a difference is if somebody were
to make their own Base/toplevel module that does not re-export Core.
However, we don't really support that situation in the first place, and
I actually think it's a feature that such toplevel modules can more
closely control the set of implicitly exposed names.

Run Details

1 of 1 new or added line in 1 file covered. (100.0%)

628 existing lines in 28 files now uncovered.

11084 of 48794 relevant lines covered (22.72%)

115450.5 hits per line