I have a lot of code running (async/go ...) blocks that I am trying to illustrate with klipse. Unfortunately, I have a lot of these problems.

I would like the output to be: AWESOME SAUCE :done

hum put the done in the go block ?

I get why this is happening, and I understand that this is entirely expected behavior. But for the purpose of illustrating what goes on in the go block I would like everything to be in order and to always output in the current klipse frame.

If I have successive frames, I think the context has moved from this frame to the next and the output goes to those (if that makes sense).

Sorry, I didn't phrase that very well, I am looking to avoid this oddity (again, it makes total sense, just makes it kind of hard to illustrate a point when the standard out is in a different frame than the (go ...) code).

oh i see, that's certainly an interesting problem =)

Yeah, sorry, that is a much better illustrating case.

you could wait in the next frame for the end output of the go block in the preceding frame

But I can only await in a go block...

or use the callback api

So I think the next frame would just be passing the buck forward in terms of the problem

this might not help clarifying your code but, you can reset a global atom to the go channel, then use something like https://clojure.github.io/core.async/#clojure.core.async/take! in next frame ?

I was able to create a atom in frame 1, conj values into the atom in the go machine, and then print the atom in frame 2 with the "repeat=1000" thing set for klipse.

But this involves needing 2 frames for every code segment, with the second frame just being a @deref-the-atom-from-the-previous-frame snippet.

Which isn't great I feel (though best I have so far).

that's some odd requirement, in order to demonstrate core.async, you have to work against it

you could cheat and write your own go and friends

Haha, yeah, I feel like that is beyond me. 🙂

i don't think that binding out would work

do the waiting in the single frame

(take! (go ... ) (fn [] (println :done)))

this illustrate one of the problems with async, it's infectious

might still pop in the next frames though

most probably the klypse people have thought about this, there is the async form for testing, there must be something in klypse, at the very least they might be interested about hearing about this problem

Cool idea, yeah, still has that issue. I don't think there is any getting around the fact that I can spin up go blocks, but I can't control when they get run in the indeterminate future.

they're using core.async under the hood it seems

Anyway, I appreciate your help @carkh, it is late for me and I should wind down for the night. Thanks for looking at this with me. 🙂

post an issue !

gnight

Hello, I'm new to clojurescript, attempting to bring in an npm dep. Does anyone know if there's any way to compile a dep that I guess requires ECMASCRIPT2018 features? I'm getting this error on compilation: ERROR: JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT2018 mode or better: object literals with spread

^ webpack alternative seems to magically work, even with :advanced optimizations. Disregard.

On June 30th, @justalanm, @ezmiller77 and @vijaykiran interviewed @jsa-aerial about interactive data visualization with Hanami&Saite. Here is the video. https://youtu.be/ld5du3L-emM To me, it was really inspiring to listen to. We will have more of this kind. The idea is to allow people to share their workflows, working with data. It is not about the perfect toolset and practices, but about the search for those. * If you have any experiments and insights about the way you deal with code, editing, data, dataflow, data-visualization – then let us interview you about it. * If you wish to help as an interviewer, that would be great, too. The scicloj-tutorials stream at the Clojurians Zulip is a good place to talk about that. https://clojurians.zulipchat.com/#narrow/stream/187445-scicloj-tutorials

I want to learn about Clojurescript Compiler; How it works, how did it implemented ? Everything. I’m reading the https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/compiler.cljc Is this a good start-point ?

Anyone ?

@scknkkrer cljs.analyzer and cljs.compiler mostly yes