Is there a way to make qualified keywords from a string? I’m thinking of for example making ::a from the string "a". Is the only way to type out the whole namespace in (keyword "very.long.namespace.name" some-string) ?

@hrmeyer What about:

user=> (defn qkw [s] (keyword (str (ns-name *ns*)) s))
#'user/qkw
user=> (qkw "a")
:user/a

Is there a point cloud library or an open 3d alternative for clojure?

what's the best way of having an atom a update when atoms b or c update? Is there something like merge-atom? Or should I use add-watch?

maybe you could just merge the state of the three atoms into one?

it's a good suggestion, but it would break encapsulation in my case; I'm now interested in the toy problem on how to merge them properly

@meditans https://github.com/martinklepsch/derivatives sounds like what you're after?

or just refs, depends on the type of operation and level of safety you want

having all state in 1 atom is way easier 🙂

ok y'all make good points, so, let give some more context on the original problem: I'm using reagent, and I have a function that takes some data as a prop. Inside that function, I want to manipulate a local copy, and sync outside my program when the local state has some properties

so, I would prefer not to put all the state in one atom because that mixes up local and global state

but I don't know how to write that I want the local state to be either a result of the user manipulation, or the change coming from the global var, whichever came last

so basically I'd like something like r/with-let [local (r/atom global)], but which continues to post update to the value

@meditans I'm pretty sure that's a react anti pattern.

@meditans it sounds like you might want to look at re-frame

I'd advise making it a fully controlled component.

in a re-frame subscription you could merge the component local and global state and then act on that

https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html

there's also the more low level reaction API for reagent and r/track, which could possibly offer a solution for this

yeah, you could also have a component which gets the merged state as props and merge that state in the parent

Also reagent.ratom/reaction seems relevant.

that's what I meant with reaction API yeah

I think I did something like this in re-find.web, lemme check

https://github.com/borkdude/re-find.web/blob/1a2cc409b2f2791324798f6e1adb13efc244b3e2/src/re_find/web.cljs#L167

(this is the website hosting it: https://borkdude.github.io/re-find.web)

thanks! give me a minute to parse all this info; you're right that it could be a react antipattern, and in fact part of this is learning what the correct patterns are (I usually write FRP, in which this problem doesn't exist)

Hey, so i'm trying to identify the value of a parameter being passed to a function. Im using emacs with cider, however, when i run the function via the repl i'm only getting back the return value of the call, not the printed value. Anyone know how i can access this?

(defn- sign-request
  ([client req]
   (println req)
   (client req)
  ))

@cgboal521 This value is printed in your cider REPL buffer

@cgboal521 You could also capture the value and then inspect it. E.g. like this: https://blog.michielborkent.nl/2017/05/25/inline-def-debugging/

Hmm, wasn't showing up but may be doing the wrong kind of repl execute in emacs. Cheers, will check that link

@cgboal521 This is also a nice read, if you want more: https://clojure.org/guides/repl/introduction

Cheers will take a look