Elements of Clojure has a great chapter on naming

https://aphyr.com/posts/340-reversing-the-technical-interview also relevant on naming 😄

just for the line

""To know a thing is to name it," you advise. True names have power. The K language was invented by Ursula K. Le Guin, and is among the oldest and tersest forms of magic. To imbue a language with a letter of your own name is to give up an element of your self. Your own initials ache at the memory."

What's the last variable name you created

jarPath

molecule

accumulate-votes

products

has anyone messed around with this? https://github.com/i-net-software/JWebAssembly

nvm, looks like it's still not feature complete anyways

What happened to https://github.com/Datomic/codeq? This looks amazing, but there hasn't been activity in many years. It seems like a kind of essential analysis one would want to perform to understand a large code base, so where is its replacement?

In the gleam of someone's eye, waiting to be developed.

?

there's a v2, but not public (yet)

... very interesting, especially if the (yet) part were to change 🙂

it's a lot easier to query now, but just one of many things in the fire waiting for an opportune time :)

Unfortunately the particularl repo I'm analyzing is a JS project, so codeq won't help beyond inspiration. I'm just surprised this isn't something everyone's doing. Git has been standard for many years now.

@alexmiller are you at liberty to talk about how analysis works on v2? That was the research topic that took my interest.

@d4hines codeq is designed to be language agnostic if you provide the right analyzer

@dominicm it's a Rich thing, so I haven't looked at it, but it's based of some I wrote for a different unreleased project, which was originally based off the first codeq. what aspect are you interested in?

I don't think that part is substantially different than the original codeq, the differences are mostly in how it's stored for analysis and querying

@alexmiller my understanding was that tools.analyzer might be used instead of matching on def*

oh, it does that in codeq 2. it's been years since I looked at either

I didn't remember codeq not using tools.analyzer

Just to check I'm following (too much double negative), codeq 2 uses tools.analyzer?

that's the part he swiped from me :)

yes

at least that is my recollection

Cool. I had thought there was some reason not to use it, so I was interested to see what the middle ground was between def* and tools.a

Does anyone use Codeq v1 at present? Would it fool-hearty to start a new DB in v1?

actually, I looked and it doesn't :)

Probably tools.analyzer had a lot more bugs circa 2012-2013, before I filed a few dozen against it, and bronsa fixed all of them tirelessly, while I was beating on tools.analyzer through my testing of Eastwood.

tools.analyzer does have one semi-notable limitation, by design if I recall correctly, of not handling the deeper uses of &env in macro definitions that a few Clojure libraries use.