-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension not loaded if trigger is a strong dependency [on 1.10] #55723
Comments
If I change julia> using Foo, ModelingToolkit
julia> Base.get_extension(Foo, :ModelingToolkitFooExt)
ModelingToolkitFooExt |
Out or curiosity, what is the use case? Since it is a strong dependency I would thought you would put the code in the package since it will be unconditionally loaded, or? |
Actually... I thought this would work looking at #54009... |
Ok, it does work on 1.11, it is just that this feature is not available on 1.10. |
Not a very compelling one, but still something I'd expect would work. I wanted to |
Yeah, that's the use case that was given in #54009 as well. |
Even if the feature is not available on 1.10, I think we ought to fix the KeyError that can happen here: JuliaLang/Pkg.jl#4018 |
The extension does not load when doing
using Foo, ModelingToolkit
:Related: JuliaLang/Pkg.jl#3797 JuliaLang/Pkg.jl#4018
The text was updated successfully, but these errors were encountered: