Wow!

wonderful!

I’ve seen/used str, s and string. I think string is the most solid - str (kind of) shadows, as you say, and s is too short. I’ve learned not to worry as much as I used to about it 🙂 But it would be neat if there were “standards” so that you could adhere to them without a second thought.

yes, I believe there is no absolute right answer in this case, and that’s why it is “Fashion”

(Let’s just hope it doesn’t change completely every six months 😂)

str. There is no shadowing b/c namespace and fns are in different "domains".

I agree with Jakub. I’d use str as I think it is fine to have a namespace and a function having the same name. Clojure knows the difference.

oh that’s a good point okay!

(btw, “Jakub” and “Jakob” @@ )

(are the names related in some way? or are they commonly used names?)

I know that there’s no technical shadowing, but I still prefer not having two things with the same name, if it can be trivially avoided.

oh @U0AQ3HP9U you stole my line 😅

I do think that avoiding “collision that ain’t technically a collision” is more for benefit of beginners who may not know the details of clojure in and out

(although in a coding guideline that fact should probably be mentioned somewhere to clear the air)

Since I work with @jakub, str, but ai should also plug that we use superstring rather than clojure.string

#solidarity :fist:

Jakob and Jakub both stem from the same old Hebrew name

@U0522TWDA that’s a TIL… you learn something new everyday, I suppose 👍

@U04V5VAUN wait, that picture in the github readme of superstring… looks like some super-advanced pure math (I’m a math major) - algebraic geometry or some string theory stuff?

(I vaguely remember the same/similar photo hang on the wall of the math department I studied in)

I think that’s an intentional pun or something.

ya that’s probably it. Hope it’s not an overkill 😀

we use string

and we have a kondo rule that warns if you use anything else!

@U0509NKGK what does that look like? (I'm thinking it might be handy to keep some aliases consistent across namespaces and projects)

https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md#consistent-alias

kondo is flippin great!

I just use whatever the code base I'm working on uses. When writing new code, I`ve typically used string but I'm not married to it and am also totally ok with str.

I use str because the docstring for clojure.string literally requires it as str .

>

It is poor form to (:use clojure.string). Instead, use require
> with :as to specify a prefix, e.g.
> 
> (ns your.namespace.here
>   (:require [clojure.string :as str]))

our team argued about it about once a year until someone lost their temper with it and added a kondo rule and refactored all the code to match it 😂

I instituted a rule in my company that I resolve all bikeshedding issues.

There ain't no bikeshedding on this ranch, if you wanna bikeshed, you come bikeshed me!

Did you get a cookie?

Or is that an American thing?

Chocolate :-)

niceeeee

:saluting_face:

It is not the only reason I keep coming there.. 😅

I would consider it for a chocolate.... it is just that they don't want my blood (and I'd probably faint as well)

I tried to give blood once (in my yoof) and I nearly passed out, that was before they even took blood!

Avoid Transylvania then 🧛

This is kind of what's possible with malli + clj-kondo

clj-kondo has a simple type system and malli is able to spit out the configuration for that, based on its own format

https://github.com/metosin/malli#clj-kondo

Wow!

Ask and ye shall receive 🙏

Very cool, Borkman!