-
-
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
docs for sort
refer to Base.copymutable
, but the latter is not in the manual
#51932
Comments
FTR, if it does get made public, it probably needs a better doc string, because I'm not sure how is one supposed to use it and/or overload it by reading the doc string. Also, FWIW, |
In 1.9 the docstring for Also, the new docstring for |
Two chagnes wrapped into one `Base.copymutable` => `Base.copymutable` & `collect` and `Base.copymutable` => `similar` & words. Followup for #52086 and #46104; also fixes #51932 (though we still may want to make `copymutable` public at some point) --------- Co-authored-by: Jameson Nash <[email protected]>
Two chagnes wrapped into one `Base.copymutable` => `Base.copymutable` & `collect` and `Base.copymutable` => `similar` & words. Followup for #52086 and #46104; also fixes #51932 (though we still may want to make `copymutable` public at some point) --------- Co-authored-by: Jameson Nash <[email protected]> (cherry picked from commit 42c088b)
If
Base.copymutable
is an internal function, why does thesort
doc refer to it? ShouldBase.copymutable
be made public?The text was updated successfully, but these errors were encountered: