https://clojuredocs.org/clojure.core/some#example-542692c6c026201cdc326940

https://groups.google.com/g/clojure/c/apkNXk08Xes/m/CGCQqLMhlHwJ

I suggest there has never been a single way. BraveClojure is still a relevant way to learn Clojure (although chapter 2 Emacs config is a little dated) There are many other books, videos or challenges websites like 4Clojure. https://clojure.org/community/resources I quite like Getting Clojure as a beginners book these days https://pragprog.com/titles/roclojure/getting-clojure/ And I’ve creates about 100 videos of coding with Clojure and a few free books which people seem to find useful https://practical.li/

Thanks

As a help, a REPL app on your phone is great for trying stuff if you're more comfortable reading away from your computer.

thanks

@U05254DQM if I follow your study group and type the same code that you do Do I then learn idiotamic clojure ?

Many of the videos that show solving the 4Clojure exercises show several different ways of solving each challenge, using more of the clojure.core functions. The more functions you are familiar with from clojure.core, the easier it is to apply valuable abstractions. The Clojure style guide covers a range of idioms in Clojure.

https://guide.clojure.style/#idioms

thanks for the answer

The clojure core predicate functions return true / false and I think that's what most people would expect from your predicate functions as well.

In mathematical logic a predicate is a statement that can be evaluated to true or false.

alright. I can work with that

On the other hand, where the 'or' operator's mathematical namesake is all about the booleans, people flagrantly use it for "return the first non-nil value in this list".

If a predicate ends in ?, the expectation is true or false. If it does not end in ?, then return truthy/falsey is reasonable.

See https://clojure.org/guides/faq#qmark_bang for more about this convention.

look how they are used there. the keys used there have (when stop (stop)) and it anticipates them being optional. then below in the body of the function there are defaults that are merged in

and destructuring will happily bind nil to bindings that aren't there

It's a form-2 component, so it returns a rendering function (the weird lambda is actually some stylised fn) and this function uses the entirety of props (the input map).

Well, :title, :on-save and :on-stop are dissoc'd so they don't get updated on rerenders, but everything else in props does.

https://purelyfunctional.tv/guide/reagent/#form-2

Thanks for all your reply. I'll look them up.

I'm not an expert but I would something like

(->> {"36" ["3" "6"]
      "42" ["4" "2"]
      "51" ["5" "1"]
      "89" ["8" "9"]
      "87" ["0" "7"]}
     (mapcat (fn [[k vs]]
               (->> vs
                    (map #(get % 0))
                    (map #(vector % k)))))
     (into {}))

Exactly that, very thanks!

Try using reagent.core/with-let instead of the current let you're initializing the value-test r/atom. That will only initialize the atom once when the component mounts instead of each time it changes.

I've tried to bring the r/atom outside the function and worked 😳 . So is atom reinizialization the problem. Didn't find nothing about it in the example/docs. Thanks! @U0CLLU3QT

Yes, when you deref an r/atom the component tracks its changes, and if you're initializing it in the same component you deref it in it will reset it on the rerender. The r/with-let is like a type two component. See here - https://github.com/reagent-project/reagent/blob/master/doc/CreatingReagentComponents.md#form-2--a-function-returning-a-function https://github.com/reagent-project/reagent/blob/master/doc/CreatingReagentComponents.md#appendix-b---with-let-macro

Whether you define the r/atom outside your component or inside a type two component (like the docs I linked to show) depends on the use case. Doing it in a type two component means that each will have their own local state, which you might want if you're planning on having multiple instances of them.