Oliver Schulz
Oliver Schulz
> But I don't think it should be a moving target of a package. Oh, no. But histograms are really pretty much self-contained in StatsBase. > However I wouldn't mind...
Pathfinder.jl has inverse-Hessian-from-LBFGS code (CC @sethaxen).
JuliaDiff/DualNumbers.jl#45 would be nice ...
Most of the load time of ForwardDiff is actually due to StaticArrays - that is, I think, only used for the Hessian, Jabobian, etc. functionality, so a package focused on...
> It is necessary for FD DualNumbers to support SpecialFunctions, NaNMath or Calculus I think if it's lightweight enough there would be a chance to convince SpecialFunctions, NaNMath, etc. to...
> On the other part, SpecialFunctions already loads ChainRulesCore Supporting ChainRulesCore would open so many doors. StatsFuns, for example, defines a lof of `ChainRulesCore.@scalar_rule`s, but there are pretty much unusable...
> One possibly crazy idea would be to move the minimal struct definitions to ChainRulesCore, as @scalar_rule could then define methods. Coming from you, that's almost an endorsement @mcabbott :-)...
>> One possibly crazy idea would be to move the minimal struct definitions to ChainRulesCore [...] > If it's just 5 ms more or so, maybe that would be Ok?...
>> DistributionsAD could just go away completely > ForwardDiff is not the main blocker, it's Tracker and ReverseDiff. Ah, sorry, you're right of course. (Full) ChainRulesCore-support in Tracker and ReverseDiff...
Something like ```julia similar(::Type{Array}, ds::HDF5Dataset) ``` might also come in handy in that context.