I used your exact profile.clj and was able to
`cider-jack-in-clojurescript`. CIDER offered me which type of connection to
use and I selected nashorn since I see no figwheel dependencies. If you
want to move to figwheel, you'll need some cljsbuild info.
Try using [cider/piggieback "0.3.5"] along
FYI.
I'm working on a ClojureScript library named kitchen-async
(https://github.com/athos/kitchen-async) in my spare time, and if you would
like more syntactic support for Promises than promesa provides (ie. alet
macro mentioned above), you might find it useful.
I know it's not totally an eleg
I appreciate all the feedback for my question and came to know that the
implementation of the async/await feature in ClojureScript is not easy as I
expected.
I agree that ClojureScript doesn't need to accept every new feature in JS
and I know that core.async is more powerful than the newly intr
One other thing: although there are some things (like the bug I cited) that
could be fixed, the other aspect of exception handling cannot be fixed
without breaking core.async, which, by design, swallows exceptions on the
producer side. David Nolen has a proposal for the
wrote:
> good point about
good point about the IIFEs, added some notes on what to fixl:
https://beta.observablehq.com/@shaunlebron/proposal-generators-and-async-functions-in-clojurescript#blockers
> [core.async] is a much more powerful abstraction which can do a lot of
things async/await can't and anything that does can
I'm generally in favor of "embracing the host" but both generators and
async/await would probably require substantial rewrites of core parts of
the compiler. It it not just about adding a small *** or *async* keyword
somewhere. The compiler will generally emit anonymous functions at various
pla
Shaun,
Your email came in while I was drafting mine. Thank you so much for
putting together this proposal. With the features you propose here, we'd
be able to do complex async code in javascript with even less code and
fewer dependencies, and we could rely on the battle tested transpilers and
po
I'm not the OP, but I'll explain why I personally avoid core.async and what
I do to get features that are roughly equivalent to async/await today.
My first issue with core.async is that you have to be very careful on the
producer-side to handle exceptions properly. If you drop an exception, at
be
thanks for posting this question. I asked about it a few months ago on
slack and apparently it has come up a few times. There is resistance (for
good reason), but here's a proposal I put together that might get
discussion going:
https://beta.observablehq.com/@shaunlebron/proposal-generators-a
Sorry for answering with a question but I have to second Andrew. What's
wrong with core.async and more importantly how'd you implement async/await
in clojurescript in terms of syntax?
-
Nik
On Thursday, May 24, 2018 at 6:44:06 AM UTC+2, Philos Kim wrote:
>
> I wonder when the async/await featu
Not familiar with async/await myself. What would it provides that you can't
already do in core.async?
Andrew Oberstar
On Wed, May 23, 2018, 11:44 PM Philos Kim wrote:
> I wonder when the async/await feature in ES8 will be introduced in
> ClojureScript.
>
> Of course, I know there is core.async
11 matches
Mail list logo
