We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From the doc ==>
(clojure.string/upper-case "bruce") ;; bad (.toUpperCase "bruce")
But looking at clojure.string/upper-case
user=> (source clojure.string/upper-case) (defn ^String upper-case "Converts string to all upper-case." {:added "1.2"} [^CharSequence s] (.. s toString toUpperCase))
it is but a call to interop. It will be nice to know why one is preferred over the other.
The text was updated successfully, but these errors were encountered:
Two reasons:
Sorry, something went wrong.
* reads better (subjectively)
Style guide by definition is subjective and this is fine with me
* portable across Clojure implementations. All interop calls tie you to the underlying platform.
That had not crossed the mind. Thanks. May I then suggest the title "Use platform agnostic methods to improve portability"
Yeah, I totally agree this should be formulated in a more generic manner.
No branches or pull requests
From the doc ==>
But looking at clojure.string/upper-case
it is but a call to interop. It will be nice to know why one is preferred over the other.
The text was updated successfully, but these errors were encountered: