Morning 😪

Morning

Morning

I might need a ✨ ☕ ✨

@manas.marthi what has you up so early?

Morning morning

mogge 😼

Mornin'

bad dreams

morning

https://stuartsierra.com/2018/07/15/clojure-donts-thread-as intersting

Bore da

https://stuartsierra.com/2018/07/06/threading-with-style slightly more interesting

Morning

The example involving def is great

o/

Morning!

in that as-> example above, the pattern I was shown was declaring a partial inline

so if you declare a partial it returns an fn and you then just make sure the arg you want is the first of the restargs

We actually avoid partial, and use #() always.

any reason for avoiding partial?

or do you mean, just in threading?

because comp + partial is a pretty useful thing...

altho I guess transducers are now the hot new newish thing 🙂

We avoid it because it makes the arguments extremely opaque, and also something about "haskell people" 😜. I think that #() does make it clearer how the function is expected to be called.

that's fair

so you mean you'd wrap the fn you want in a higher order #() construction?

I actually prefer partial to #(), I find it easier to reason about, I know that it was the first args that have been curried and usually implies you’ve thought about the order of args. Whereas #() you could have curried curried any of the args to the function and I need to read closer which ones you’ve curried

@alex.lynham yeah.

@firthh interesting, I have the opposite mentality. I immediately have to figure out which arities the callers of the f will be using, and it is a pain. Where as with #() I know exactly what is expected.

Interesting, I suppose #() is more explicit

I like explicit 🙂 My code is horribly verbose.

I even dislike conveniences over consistency like [clojure.string :as str] vs [clojure.string :as string]. Always the latter!

While I like explicit I suspect I might go for the former ^^

I'll hold my hands up and say I probably would go for the former there :)

I don't understand why string is special and is renamed to str when everything else is just has clojure. dropped off the front.

I dunno, a lot of the clj I've seen gets ns's crunched down to as few chrs as possible

yeah, I see that too. It confuses the hell out of me. In one ns my.cool.app.models is models/ and in another my.cool.app.db.models is models/, I can't cope with the congitive overhead.

I want ONE alias per project, don't care if it's long, I have auto-complete for that.

The other one is utils, web-utils :as utils then app.utils :as utils I just, urgh!

yeah so that's a good example

bc I've seen a lot of code where that would be

:as wu :as au

gross

The correct answer is [app.models :as models] and [my.cool.app.db.models :as db.models]

(correct to me of course, pushing my grumpy perspective on the world)

https://stuartsierra.com/2015/05/10/clojure-namespace-aliases largely I think this

[app.models :as models] as [app.models :as mooodles]

:thumbsup:

hahaha

idk I tend to think as long as it's consistent within a project, it's whatever rolls off the keyboard and reads best

in most cases that'll be the full word, but sometimes if it's better to be terse then I'll take wu au dbio fio or whatever

Separately, having read the original threading with style…

Don’t you think that what he calls a blackboard / context map is simply procedural namespace?

and tbh if I'm only using it once in a ns (e.g. a fn in clojure.string) I'll sometimes just use the full path, clojure.string/join or whatever

@alex.lynham you require it first though right? 😄

well, if it's in the project deps then it's available to you via that path

(unless I've misunderstood yr question 🙂 )

no it isn't. You have to require a namespace before using it.

Else it might not be loaded.

hm, looking through source code it looks like I'm lying, it is required and I don't really see a case where I've got it as a full path

java classes work how you describe.

though I did find an example of terse requires

:as ncio

because it's not io but you want to signal that the other namespace is the input and output boundary of your program

bc :as io isn't included in that ns but it's used elsewhere in the project

contrived example maybe

But why not just http://needlecast.io? 🙂

^

i would opt with that too

ncio is not as nice as http://needlecast.io

ah that's because I don't like the . character in an alias

...which sounds irrational when you write it down

but it's not, I promise 🙂

(okay, maybe a little bit)

I'd go with http://nc.io if I was using it a lot.

I'll go with the grain of the project but yeah probably prefer the shorter one. If other people got upset in review I'd either use the longer one or

yeah

Just when I thought my thing was working, it looks like the db transaction is rolling back silently...

this is definitely a job for first thing in the morning with fresh coffee