Hello, all! I am trying to write a clojure.spec to ensure that a function argument is actually an atom, as opposed to one that’s already dereferenced. I ran into this post, which was great (thanks, 2016 version of @alexmiller! 🙂 https://stackoverflow.com/questions/58700950/persistentvector-cannot-be-cast-to-class-iatom So this works in Clojure REPL:

(instance? clojure.lang.IAtom (atom {}))
=> true

(instance? IWatchable (atom {}))
=> false

(type (atom {})) is cljs.core/Atom. So i tried (instance? cljs.core/Atom (atom {})). But i don’t know if that’s a robust solution but seems straightfoward

In cljs/core.cljs, there's this thing that built-in atoms use:

(defprotocol IAtom
  "Marker protocol indicating an atom.")

Reagent uses it:

{:pre [(satisfies? IAtom a)
         (ifn? f)]}

(defn- atom? [x]        
  (satisfies? IAtom x))

Trying to run material-ui 5.1.0 / emotion-js / React with shadow-cljs I get a file-name too long error from @emotion/react hoist file https://github.com/emotion-js/emotion/tree/main/packages/react/isolated-hoist-non-react-statics-do-not-use-this-in-your-code I am running Ubuntu 20.04.3

FileNotFoundException: .shadow-cljs/builds/elephantchess/dev/shadow-js/module$node_modules$$emotion$react$isolated_hoist_non_react_statics_do_not_use_this_in_your_code$dist$emotion_react_isolated_hoist_non_react_statics_do_not_use_this_in_your_code_browser_cjs.js (File name too long)
        java.io.FileOutputStream.open0 (FileOutputStream.java:-2)
...
        shadow.build.cache/write-file (cache.clj:24)
        shadow.build.cache/write-file (cache.clj:24)
        shadow.build.closure/convert-sources-simple/fn--12746/fn--12748 (closure.clj:2113)

hmm this has come up before. I guess I'll need to add something to shorten the filenames somehow

or can you increase the file name max length on ubuntu somehow?

I've got a feeling it is built in to the ext4 filesystem maybe I can partition with a new fs

well I can just shorten the name after a certain length. didn't expect anyone to use such long filenames ... but I guess everything exists on npm 😛

maybe reiserfs, if I can overcome scruples

I'm still wrestling to understand the purpose of that file; it is intriguingly named

according to the internet the max file name length is 255 bytes

I think materialui is a common library, so I'm guessing alot of people will trip over this

but the filename is only 193 bytes?

only appears to be a linux issue. windows and mac seem to be fine

yeah I didi not understand the length

Hi all. Any thoughts on this re-frame code? It’s a basic input field, I’m trying to keep track of its value, and I’m rendering its value to a separate div. As written, it has some kind of performance problem, I’m not 100% sure why. (code in thread 🧵)

Looks like ClojureScript 1.10.879 and 1.10.891 behave differently when passing a map to a function that accepts keyword arguments:

λ clj -Srepro -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.879"}}}' -M -m cljs.main --repl-env node -e '(defn destr [& {:keys [a b] :as opts}] [a b opts]) (destr {:a 1})'
#'cljs.user/destr
[nil nil {{:a 1} nil}]

λ clj -Srepro -Sdeps '{:deps {org.clojure/clojurescript {:mvn/version "1.10.891"}}}' -M -m cljs.main --repl-env node -e '(defn destr [& {:keys [a b] :as opts}] [a b opts]) (destr {:a 1})'
#'cljs.user/destr
(node:62287) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the AsyncResource class instead. (Triggered by calling emit on process.)
(Use `node --trace-deprecation ...` to show where the warning was created)
Execution error (ExceptionInfo) at cljs.repl/evaluate-form (repl.cljc:577).
Execution error (Error) at (<cljs repl>:1).
No value supplied for key: {:a 1}

(The node deprecation warning is unrelated, dunno what that's about.)

(Also, it seems that there's 1.10.893 in Maven Central, but there are no release notes for it.)

looks like a bug to me. best report it to jira or http://ask.clojure.org. slack tends to get lost

All right, will make an Ask post about it.

hmm maybe its not actually a bug. CLJ behaves the same

Right, CLJ (prior to 1.11.*) behaves the same as 891. Our codebase had a couple of bad calls like that where things worked regardless with 879, but with 891 they throw.

@flowthing it's because a map bug was fixed, which is in the change log

Hmm, not sure which change log entry you're referring to, but all right.

@flowthing sorry, you were right, this one was missing added

was not intentionally left out - why I thought it was there - thanks for pointing it out

If I wanted to create a website and wanted to make sure google saw it properly, should I use fulcro (which I know does awesome ssr) or can I use re-frame like I want to with some library?