Fork me on GitHub
#core-async
<
2020-06-25
>
tianshu18:06:53

yes, alt! doesn't return a channel, but this error looks like you can't pass keyword as argument to alt!.

tianshu18:06:05

ran into a weird issue, I just update core.async to the latest version, when I do (require 'clojure.core.async) an error tell me ClassNotFound for clojure.core.async.Mutex. But after some searching, I think there's no such Class or symbol in core.async code base.

noisesmith18:06:13

that file was last edited in 2013

tianshu18:06:48

but the latest version doesn't have java code anymore

tianshu19:06:11

maybe I shoud clear the target directory

3
noisesmith19:06:15

that's true - the java code is still in github, but the released artifacts for recent versions don't have the classfiles

noisesmith19:06:07

but also, the references to Mutex are removed from the clojure.core.async.impl.mutex ns

noisesmith19:06:16

what file is it trying to load when you see that error?

noisesmith19:06:36

also, I wonder why the github code doesn't reflect recent releases

hiredman19:06:32

Why don't you think it reflects recent releases?

noisesmith19:06:15

in github, theres a Mutex.java, in the jar from maven, there's no corresponding class file, and the mutex definition doesn't use that class any more

hiredman19:06:16

And the pom isn't setup to compile Java code

hiredman19:06:26

So there is nothing to package

noisesmith19:06:05

oh, I missed this, you're right. Mutex.java is still in the repo, but is now a no-op, and the mutex impl doesn't try to use it any more

hiredman19:06:55

It doesn't appear to be in the repo any more at least on master either

noisesmith19:06:00

I must have ended up looking at the wrong version due to bad github js or user error

danboykis21:06:01

@U0NBGRGD6 i had a similar problem some time ago and i had to do a dependency tree in order to figure out what was bringing in a very old version of core.async

danboykis21:06:52

i don't recall exactly what it was anymore but i vaguely remember something with an old clojurescript version

tianshu03:06:43

Yes, I finally solve the problem by delete the target directory.

noisesmith18:06:11

the error is from (<! (alt! ...))