You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say I have a module TopLevel that I want to @require a package (e.g., ProgressMeter)
module TopLevel
using Requires
__init__() =@require ProgressMeter="92933f4c-e287-5a05-a399-4b506db050ca"println("ProgressMeter loaded!")
using Main.SubModule # this uses ProgressMeter internallyend
and I have a sub-module that itself uses ProgressMeter:
module SubModule
using ProgressMeter # used internal to "SubModule"# ...end
The TopLevel module will always think ProgressMeter is loaded because of a sub-module that uses it internally.
This means for the TopLevel package, I cannot @require any packages that are used by dependencies (some of which may be unknown to the developer of TopLevel, causing head-scratching behavior 😄)
Is there a way to ensure that the scope of the @required package is limited to modules "outside" the top-level module?
The text was updated successfully, but these errors were encountered:
Say I have a module
TopLevel
that I want to@require
a package (e.g., ProgressMeter)and I have a sub-module that itself uses ProgressMeter:
The
TopLevel
module will always think ProgressMeter is loaded because of a sub-module that uses it internally.This means for the
TopLevel
package, I cannot@require
any packages that are used by dependencies (some of which may be unknown to the developer ofTopLevel
, causing head-scratching behavior 😄)Is there a way to ensure that the scope of the
@require
d package is limited to modules "outside" the top-level module?The text was updated successfully, but these errors were encountered: