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
I'm willing to define some rules for SpecialFunctions, however some of the derivatives require functions not implemented in SpecialFunctions but in say GSL.jl. Is there any style convention for only allowing rules that are closed under derivation in the same package? I suppose the worst that can happen is that a user would get an undef error if they try to use a rule that requires GSL.jl but they have not loaded it before.
The text was updated successfully, but these errors were encountered:
This sounds OK to me, better than not having the rules, or unconditionally loading. I don't see a way to make a very friendly error message, sadly... it's a pity that GSL doesn't have a more verbose descriptive name.
I'm willing to define some rules for
SpecialFunctions
, however some of the derivatives require functions not implemented inSpecialFunctions
but in sayGSL.jl
. Is there any style convention for only allowing rules that are closed under derivation in the same package? I suppose the worst that can happen is that a user would get an undef error if they try to use a rule that requiresGSL.jl
but they have not loaded it before.The text was updated successfully, but these errors were encountered: