Hello, is there a way to do redirection for GET/POST requests with ring? Like I want to be able to temporarily preserve backwards compatibility such that GET/POST to /_crux/query to become GET/POST in /_xtdb/query . I know there is ring.util.response/redirect that doesn't seem to help for when it is a query. And I quite seem to get the handler needed unless I am to modify the library

Honest question: We tend to prefer requiring stuff with :as over using :refer or use. Why?

both remove context from the function at the point of use

if you just see foo ,you have no indication of whether that's in the current namespace or from elsewhere (and with use, you really need some level of static analysis to even tell where it came from). with refer you at least have a list at the top of your file

for functions/macros acting as syntax, this removal of context can actually be a feature (like refer'ing >! from core.async or a defwhatever macro)

Namespace prefixes aide me in both reading and writing code. Knowing where a function comes from at a glance is so nice. I really miss this every time i take another stab at using a scheme or other lisp. For writing, the prefix helps for autocomplete so much. And I just recently felt the pain of use when a var with the same name was in both namespaces. I copied a var from the test ns and put it into the main namespace, and then later went into the test namespace. Since it used :refer :all on the original namespace, I had a collision of var names. Super annoying. And this pitfall exists everywhere you use use. Changing one namespace could break consumers anywhere. It is a nightmare

(I think that macro as syntax heuristic is really tasteful. Gonna incorporate that)

a little bit goes a long way :)

I never get dogmatic in my style. And its a good rule of thumb for how to decide when to use refer. So thanks 🙂

use CMD-Shift-Enter to post a snippet

that’s an enormous block of text and I think you are asking for help making javascript code, which we aren’t really experts at here.

Interesting discussion about identifying special forms in editor for highlighting, #{let fn letfn loop} all report :special-form true in their metadata despite not being special forms and not being in (clojure.lang.Compiler/specials).

if it has metadata it isn't technically a special form

special forms have no vars to hang metadata on

macros and special forms behave differently in regard to shadowing

agree. so it sounds like anything reporting to be :special-form is lying almost by definition

special forms basically define an interface between the language and the compiler and it is not surprising that you might want some kind of facade over that, and macros are an attractive way to implement that facade

but yeah, you cannot substitute a macro for a special form and have it work the same in all situations

and you cannot really hide the "real" special forms anyway

yeah. i think this is just for syntax highlighting. and someone pointed out some things were both a macro and a special form which caused a double take leading us here

i don’t believe any of this is semantic and just started with thrown being highlighted as a macro.

it is a whole thing and a half

"special form" is not some much of a prescriptively defined notion, but something that just kind of arises out of writing a lisp with macros, the macros have to bottom out at some base language, and that base language needs to be understood by eval

Hey all; does anyone know how I can set a namespace, if I am calling into the clojure compiler from java? I am trying

Compiler.eval (RT.readString ("(in-ns 'user)"));

Exception in thread "main" java.lang.IllegalStateException: Can't change/establish root binding of: *ns* with set

and, despite commonly referring to special forms by the symbol that is the first part of the list, it is the whole list that is the special form (why it is a special form and not a special symbol)

*ns* is basically "compilation context", it is used when compiling forms to resolve symbols, so if you are outside of a place where compilation is known to be happening (the repl, loading a file) then it won't be bound and not settable

you can bind it yourself

the same way the compiler does var binding

for syntax highlighting the best thing to do is come up with your own name "most favored symbols" and then make those whatever you want, and it will always be correctly because it is your name and you define it

@hiredman The issue is a bit more general than syntax highlighting: the clj-kondo static analyzer emits information that other tools (like clojure-lsp) use. Should clj-kondo say in its analysis that when clojure.core/fn is called, that this was a special form invocation or not? The medadata :special-form makes this a bit blurry.

Perhaps it should follow what tools like tools.analyzer do, I haven't checked there, but I expect that it only says "special form" for special-symbol? stuff

Hmm, no it seems tools.analyzer doesn't add that info

https://github.com/clojure/tools.analyzer/blob/fd55a292ff4802bd7b7e8b78036d0d1e25f6e48b/src/main/clojure/clojure/tools/analyzer.clj#L218-L222

Yes, that thing isn't really used in the output

yeah

But I would say it's the "correct" answer, and the other things are just macros

but like catch isn't a special form

(try ...) is a special form and catch is part of its dsl

user=> (let [catch identity] (catch 1))
1
user=>

Agreed. It also doesn't behave like a special symbol here:

user=> (let [catch (fn [] :foo)] (catch))
:foo

🙂

@ericdallo In any case, you can use special-symbol? + the clojure.core namespace to determine yourself in clojure-lsp if it's a special form.

user=> (clojure.set/difference cljs-specials clj-specials)
#{defrecord* ns* ns js*}
user=> (clojure.set/difference clj-specials cljs-specials)
#{monitor-exit reify* clojure.core/import* monitor-enter}

ish