Make sparsity detection and coloring interfaces public

[adrhill]

Closes #82.

[gdalle]

thanks!

[gdalle]

While we're at it, we may as well do them all

[gdalle]

Since the discussion in https://discourse.julialang.org/t/is-compat-jl-worth-it-for-the-public-keyword/119041/ has come to a close, I think I'd rather put all the public declarations for ADTypes in one file, which makes the following approach the most appealing:

if VERSION > ...
    include("public.jl")
end

[adrhill]

Looking at the "likes" on Discourse, it looks to me like most people favor Mason's macro-based solution, which is what is implemented here as of 1cd4162. The disadvantages of a separate src/public.jl file have been discussed on Discourse as well.

Have you taken a look at the current diff? I think it's simple, succinct and readable.

[adrhill]

I'm obviously biased towards my own code, but I like the clean overview it provides in the main file, separated by use-case:

# Automatic Differentiation
export AbstractADType
export AutoChainRules,
       AutoDiffractor,
       AutoEnzyme,
       AutoFastDifferentiation,
       AutoFiniteDiff,
       AutoFiniteDifferences,
       AutoForwardDiff,
       AutoModelingToolkit,
       AutoPolyesterForwardDiff,
       AutoReverseDiff,
       AutoSymbolics,
       AutoTapir,
       AutoTracker,
       AutoZygote
@public AbstractMode
@public ForwardMode, ReverseMode, ForwardOrReverseMode, SymbolicMode
@public mode
@public Auto

# Sparse Automatic Differentiation
export AutoSparse
@public dense_ad

# Sparsity detection
export AbstractSparsityDetector
export jacobian_sparsity, hessian_sparsity
@public sparsity_detector
@public NoSparsityDetector
@public KnownJacobianSparsityDetector
@public KnownHessianSparsityDetector

# Matrix coloring
export AbstractColoringAlgorithm
export column_coloring, row_coloring, symmetric_coloring
@public coloring_algorithm
@public NoColoringAlgorithm

[gdalle]

In the spirit of maintainability, I would like to avoid macros whenever I can. But I don't feel very strongly about this so if others prefer this way I'll yield.

[adrhill]

As you know, I generally agree with that sentiment, but in this case the macro simply returns Expr(:public, args...).

[gdalle]

I added CI on 1.11 in #84. Can you merge main into this PR and maybe test that everything works on 1.11, i.e. that the symbols are indeed marked public by the macro?
Also for some reason I didn't see code coverage?

[adrhill]

Also for some reason I didn't see code coverage?

Looks like it wasn't triggered on previous PRs either. The codecov PR page looks odd as well, with all PRs being untitled. Maybe just the usual codecov bugginess?

[gdalle]

Fair enough. Are the symbols correctly marked on 1.11?

[adrhill]

How do I check this? By looking at the docstrings in REPL help mode?

[gdalle]

I think the easiest is to add a test that only runs on 1.11 and that verifies whether the unexported Symbols we marked public are part of names(ADTypes).
https://discourse.julialang.org/t/what-does-the-new-public-keyword-actually-do/108975/3?u=gdalle

[gdalle]

perfectly balanced, like all things should be