Is it possible for me to use typed ES 6 code in my clojurescript project?

It’ll have to be compiled down to runnable js. http://lukevanderhart.com/2011/09/30/using-javascript-and-clojurescript.html goes over it pretty well (although not specific to es6 code)

@jm: I am currently using google-closure library style JS, pretty similar to this project - https://github.com/gfredericks/goog-integer

It looks like the closure compiler has native support for typed ES6, so I was hoping I could slap a comment at the top of the file or something and it would do its thing.

I mean I'm adding types in my JSDoc strings anyway, might as well do it for real

@xcthulhu I didn’t realise closure compiled typed ES6, where are you reading that?

@jm: Here https://groups.google.com/d/msg/closure-compiler-discuss/5EVAw6oO2BI/kJfMJwnTKBEJ

@xcthulhu thanks, I’m not aware of any support for it, sorry I can’t be much help. Discussion in https://groups.google.com/forum/#!topic/closure-compiler-discuss/5YJJu5BEndQ might be relevant, sounds like they may have moved focus.

@mfikes does Planck repl have interop with OSX libs like through Obj-C ?

@octo221 No. All of the Obj-C code that interoperates with low-level stuff is essentially hard-coded.

In addition, Planck is moving away from Obj-C, to C, for portability.

Cool! Is that portability in the not-just-OS-X sense, or something else?

I love Planck, but I also appreciate that it only works because I have a Mac anyway.

@lvh Yeah, it exists for Linux now.

Awesome. Thank you!

http://planck-repl.org/download-alpha.html

I didn’t know JSC ran on other platforms; that’s pretty cool.

@lvh it should run on Windows too I thought (not sure how much work is involved)?

@lvh In addition, JSC ships with Ubuntu 16.04 Desktop, and the Planck 2.0 alpha makes use of it.

Hey all, with the new macro stuff, I was hoping to be able to use (:require [clojure.core.async :refer [go]]) but that still seems not to work in cljs 1.9.216

@timgilbert: macro inference only works when the macros/non-macros namespaces are the same

Ah. Any plans to unify this interface between clojure/clojurescript?

In your case you still need to require-macros cljs.core.async.macros

@timgilbert needs to be fixed in core.async, but a pretty huge breaking change

so questionable whether it’s worth it

but probably worth opening an issue about

I see, thanks @dnolen. I'll file a ticket just to have a place for discussion

@timgilbert I would check first it doesn’t already exist of course

I didn't see it in an initial scan of JIRA but I'll look a bit more closely

ClojureScript 1.9.225 released https://groups.google.com/d/msg/clojurescript/MF8QfYkIDOs/HsIu7iKEDQAJ

Ah, there is an existing issue about combining cljs.core.async.macros and cljs.core.async: http://dev.clojure.org/jira/browse/ASYNC-119

I'll add a note to that ticket about the latest developments

@timgilbert I suspected as much

I believe the macros could be moved without breaking the API: macros can be moved to the main namespace and then the macros namespace could have wrappers (not sure what to call these) for compatiblity

Yeah, I just added a note to that effect on the ticket

@juhoteperi not a bad idea, somebody should submit a patch for that

@dnolen: Just working on it

Aaand I think I got it working

The change will be breaking if the user is using same alias with both macros and normal ns, but that was already deemed unsupported, so I don't think that is a problem

I guess most are using :refer with core.async macros

And patch attached 🙂

@juhoteperi: sweet!

I'm using secretary for routing, and I want to link to a certain element, like https://github.com/clojure/clojurescript#getting-started I've had no luck so far, any tips?

@curlyfry: The keyword you're probably looking for is "fragment" (the bit after the hash in a url). It looks like there's an open PR in secretary about fragment handling: https://github.com/gf3/secretary/pull/84

Hmm, I guess that's more about parsing them though...

@timgilbert: Thanks, but yeah, still not making much progress