cossio
cossio
> In my experience the code quality of community-maintained packages is better -- more eyes to look at the code, more chances to keep up with the evolving Julia standards,...
@simonbyrne One (probably inefficient) way of doing it is to rely on `erf(::Complex{BigFloat})`, which is already defined. ``` myerfi(x::BigFloat) = imag(erf(x*im)) ```
new issue https://github.com/JuliaMath/SpecialFunctions.jl/issues/119
Now that #119 is closed, perhaps we can add `erfi(x::BigFloat) = imag(erf(x*im))`?
I'm running into this problem. In case details differ a bit and it's useful, here it is: ``` $ curl -fsSL https://install.julialang.org | sh /tmp/tmp.yutIGUX4TE/juliainstaller: /lib64/libc.so.6: version `GLIBC_2.18' not found...
Hopefully this fixes https://github.com/JuliaLang/juliaup/issues/321.
> A non-breaking fix is for each private registry user who also uses General to use the 3 day waiting period to monitor for clashes in new package registrations to...
What if we have a list of "trusted" / "untrusted" registries for each package? When a package is installed for the first time, it's registry of origin (call it registry...
Why not just ask the user whenever a package is present in more than one registry, which one to use? That is, for each package detected to be present in...