Skip to content

Commit a576cd0

Browse files
authored
Only implicitly using Base, not Core (JuliaLang#57357)
Inspired by the question in JuliaLang#57311 (comment), 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.
1 parent 24bd9d4 commit a576cd0

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/typeinfer.jl

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ being used for this purpose alone.
1010
"""
1111
module Timings
1212

13+
using ..Core
1314
using ..Compiler: -, +, :, Vector, length, first, empty!, push!, pop!, @inline,
1415
@inbounds, copy, backtrace
1516

0 commit comments

Comments
 (0)