You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in trying to use core.async from javascript. I know that js-csp exists and is great, but, in the same way that mori leverages real world usage and benchmarking through ClojureScript, using the actual core.async implementation offers the same benefits.
Would adding core.async functionality be desirable, or is it beyond the intended scope of mori? I can see an argument for keeping mori focused on immutable data structures (although it does include transducers and some extras now). If mori should remain focused on immutable data structures, would it be desirable to expose core.async via another "extras" type submodule, or create its own separate project?
I tried to mess with this a bit, but the ClojureScript build process is a bit foreign to me, and I noticed from #155 that there may be some issues with the build script right now. I tried the build approach from #155 and then testing using the mori/support files, but that wasn't working for me. I think I can work around this to try building and testing, but before I proceed any further I wanted to ask:
Are there any special considerations that would make exposing core.async to javascript difficult? (my impression is no, since core.async obviously runs in javascript)
Is there any interest in adding this to the mori extras, or in having it as a standalone library?
Is there a recommended method for building and testing this?
Thanks!
The text was updated successfully, but these errors were encountered:
I may have been mistaken in believing this is really possible. While core.async is obviously usable in a javascript environment, the use of macros probably means the compilation step is required.
I'm interested in trying to use core.async from javascript. I know that js-csp exists and is great, but, in the same way that mori leverages real world usage and benchmarking through ClojureScript, using the actual core.async implementation offers the same benefits.
Would adding core.async functionality be desirable, or is it beyond the intended scope of mori? I can see an argument for keeping mori focused on immutable data structures (although it does include transducers and some extras now). If mori should remain focused on immutable data structures, would it be desirable to expose core.async via another "extras" type submodule, or create its own separate project?
I tried to mess with this a bit, but the ClojureScript build process is a bit foreign to me, and I noticed from #155 that there may be some issues with the build script right now. I tried the build approach from #155 and then testing using the mori/support files, but that wasn't working for me. I think I can work around this to try building and testing, but before I proceed any further I wanted to ask:
Thanks!
The text was updated successfully, but these errors were encountered: