-
-
Notifications
You must be signed in to change notification settings - Fork 16
export Base.LinAlg.chksquare
#292
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
Comments
I gree that it would be a useful function to expot, but I don't like the |
I will try submitting a PR, as I mean to learn the workflow anyway and such a minor change would be a good place to start. |
This could be used elsewhere without exporting it, just by qualifying it with the module name. I'd be in favor of renaming and documenting it, but not exporting such a trivial thing. |
If the name is changed it should be deprecated even though it is a non exported function. It is likely used in many places out of Base. |
How about renaming it to |
How would I note in the documentation that it is not exported? Is there a convention, eg using the full form |
Or just |
To clarify, |
What about |
I think |
+1 for |
I just submitted PR JuliaLang/julia#14601, which should close this. Thanks for all the help. |
Rationale: checking that a matrix is square is a pretty common operation. While
chksquare
is a minor utility function, it is well-designed, useful, and allows standard error reporting. Without a common function, libraries end up implementing their own solutions or explicitly spell out something likeor one of the countless variations. Standardizing this outside
Base.LinAlg
would be useful.The text was updated successfully, but these errors were encountered: