-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider exporting StatsBase.sample
from Statistics
stdlib
#32343
Comments
StatsBase is not a part of the Julia stdlib so how can Statistics reexport the names? Also, the general philosophy is to try move things out of the Julia repo so
would mean to move the code in Statistics to StatsBase. |
I'll note that there's still work on moving things in the direction StatsBase -> Statistics |
I am confused about the names. I thought that There are multiple packages doing slightly different things:
I understand that |
Initially I thought that StatsBase.jl contained the foundations for stats-related work. Including all possible names. Then a package like Now I learned that StatsBase.jl is not even used by Statistics, I am not sure if these directions are clear to everyone. |
Yeah, since StatsBase isn't used by Statistics there is nothing that can be reexported. |
StatsBase is supposed to be removed at some point, after its features have been moved either to Statistics or to more specific packages. Not sure which applies here. |
That sounds like a good plan. Moving the functionality to either Statistics or some other specialized packages seems helpful. |
This is a feature request to consider exporting basic names such as
sample
defined in StatsBasefrom the
Statistics` stdlib.Right now whenever we need access to the
sample
function, we need this extra import, which seems suboptimal:It seems reasonable to reexport StatsBase from Statistics. That would solve a bunch of name-related issues:
The long-term solution is to move the code as well, but meanwhile, I think we could just reexport the names.
The text was updated successfully, but these errors were encountered: