Question about new "package extensions"?

I realize some of the docs may still be getting filled in prior to 1.9 release, but couldn’t resist asking about this potentially really nice new feature. Two questions:

  1. Say my package Foo has an optional dependency on CUDA.jl (as I understand specified by a [weakdeps] entry). When I add Foo, does CUDA get installed?

  2. Say Foo has a weakdep on CUDA and a corresponding compat entry CUDA = "4" but I try to install Foo into a parent environment which is explicitly restricted to CUDA = "3". Can Foo still be installed here? Just the package extension will not be loadable?

No. The point is that the user can opt into the extended functionality by adding CUDA. The “entrypoint” to the extension for this case would probably be to pass a CUDA array, so then you have, of course, installed CUDA.

Yes, and yes, since the weak dependencies are not hard requirements.


Would there be a way for the user to know he needs to update Foo in the following situation? CUDA@4 and Foo@1.1 are installed, Foo@1.1 has a weakdep on CUDA@3 and Foo@1.2 weakdeps on CUDA@4.
I can imagine lots of confusion in such cases.

Awesome, that’s exactly the answers I was hoping to get!

I do agree with @aplavin, it would a nice addition if there was a way for the user to know that a compat bound is preventing a package extension from loading. Maybe exposed in pkg> st -m?

Two other minor things that came up while I was trying this out briefly:

  1. For a package I’m developing Foo, if I using Foo and it errors, in the same session I can fix the error and try again until it loads. For package extensions, if it errors, is there a way to trigger trying to reload it? Or do I have to restart my session? Would be nice not to have to.

  2. With @require one thing I found nice was the ability to trigger exports in the main package. Like:

    module Foo
    @require Bar="..." begin
        some_foo_bar_specific_function(x) = ...
        export some_foo_bar_specific_function

    Is there anything like this with package extensions?

If I file any of these as issues, is the right place the julia or Pkg.jl repos? In any case, really great to have package extensions in the main language, super useful!

There is status --extensions which will show some extension related information, so you will at least see if the extension is active or not.


Not really. The main “entrypoint” of an extension is new method dispatches. You can define and empty function and export it regardless though. Me and @kristoffer.carlsson have discussed this quite a bit so maybe he will chime in. Some of this is also discussed in JuliaLang/Pkg.jl#3282.

Pkg.jl probably, to start with.