does anyone know how I can do % keyframes with Garden?

ah sorry wrong room

Hi, what is the clojurescript equivalent of clojure’s extend function?

there's no extend in cljs

pbaille: rather, there's no extend, but there's extend-protocol and extend-type

ok but i need to extend at runtime

thanks

no way?

Maybe you could put something together but extend is not implemented in cljs

there is also specify!

it is also a macro

i really need a function

there’s a proposal for dynamic extend by cemerick a while ago but don’t know if it concretized

is it possible to define a protocol in one project, have it compiled down to js and then refer to that protocol in another project and extend it there?

@emil0r: no you are going to need the cljs

is it possible to have the project in your project.clj file and extend it from there and then load the two js files one after another?

or would the code clash

ie. project 1 has the protocol. i compile the js file. project 2 has project 1 as a dependancy, extends the protocol in there, compiles to another js file

website x referes them in order

refers*

you are going to need to source .cljs for advanced compilation

well not for advanced compilation but for the cljs compiler to emit the correct code for the procotol

so the source defprotocol is needed, it cannot be reconstructed from .js

@emil0r: it is possible to use ^:export on protocol methods, FWIW. I've used this to call upon protocol implementations from Objective-C with :advanced. (`TableViewDelegate` in Goby, for example.)

ok

thanks

@richiardiandrea: there are no Namespace objects in ClojureScript. The ClojureScript wiki is pretty good about covering the language differences between Clojure & ClojureScript.

Sorry for repeating questions, but I think they get lost because of unlucky timing. I will be grateful for responses. * Why Atom doesn't implement ISwap and IReset, but there are special cases in swap! and reset! functions? For performance reasons? * Do watches prevent atom GCing (I guess not, but want to check)?

@ul just perf, protocols bring overhead

and the standard atom is a fundamental state management tool

thanks for confirmation!

nothing in ClojureScript prevents GCing

(beyond obvious stuff like top levels)

is there a way to emulate clojure’s extend function in cljs?

@pbaille: no but there’s less pressure since JavaScript is already fully dynamic

so you can’t do it syntactically but you can do it effectively.

if someone wants to submit a patch that implements extend via specify!, that would be welcome

thank you i will try

I have (:refer-clojure :exclude [get set!]) but still get a compile-time exception wrong set! usage. Any ideas?

(I have a custom (defn set! [...] … in the same namespace)

Is exclusion not possible because set! is a special form?

works for me?

hmm but I don't even get a warning if I (defn set! []) without the exclude

ah you get the warning for using set! ...

@thheller: I get the exception on the line set! is invoked, not where it’s defined, have you tested invocation too?

yeah sorry .. I just testing putting it in and not calling it 😛

and yes that probably is due to set! being special

I assume there’s nothing that can be done about this right? (i.e. file under “known limitation”)

probably not without breaking a whole lot of stuff

set! is used by many things (eg. deftype, defrecord)

ok. (def set! set!*) it is then. using set!* in the impl namespace and using set! when used in other namespaces

@martinklepsch: special forms are actually reserved

same as Clojure

If they are reserved potentially def’ing them should cause at least a warning?

not sure what the behavior in Clojure is here

but happy to take a warning for ClojureScript

cljs.reader/read-string is closer to clojure.edn/read-string than it is to clojure.core/read-string — is that correct?

yep

Would you take a patch updating the docstrings for read & read-string indicating they’re safe in contrast to clojure.core/read-string? Found this pretty confusing and the only answer I could find was in this lenghty SO answer: http://stackoverflow.com/questions/24661655/clojure-clojurescript-clojure-core-read-string-clojure-edn-read-string-and-c

yes minor ticket for that + patch is fine

can I see from outside an API that tells me if a symbol is a special function? kind of like Mike's:

(defn repl-special?
  [form]
  (and (seq? form) (repl/repl-special-doc-map (first form))))

I see that in cljs is is-special-fn? (set (keys special-fns))

but it is in a .cljc...maybe we could refactor and expose repl-special-doc-map somewhere?

@richiardiandrea: what would be the point of this?

😄 sorry maybe my knowledge of cljs.repl and cljs.js is not complete

but

how can I print doc of a symbol? I saw that in repl.cljc there is a doc macro, but still, in planck Mike copied over the special-doc-map and repl-special-doc-map

but I am trying to figure out don't worry

it looks like i cannot pass (doc in-ns) like this to cljs.js/eval-str

@richiardiandrea: cljs.js is a new thing that very few people actively use & making Clojure like runtime stuff work in it is non-goal

@martinklepsch: on defing reserved words, I have an old ticket that is somewhat related. what if you def a namespace alias? http://dev.clojure.org/jira/browse/CLJS-1271

so issuing warnings on def for a set of reserved words, namespaces and the such could be useful to prevent unexpected behavior for people who misuse def

@dnolan, can I ask you a question... I see the -evalute protocol fn is called on each evalution...but in case of a browser, just send-for-eval to it

@richiardiandrea: I do not understand what you are asking

what happen next? How the browser evaluates?

sorry for the newbie question 😄

ah ok I found clojure.browser.repl/evaluate-javascript is it this the evaluation function for a browser?

I don’t have time to give detailed explanation about how the REPL stuff and cljs.js bits work, sorry

ok thanks anyways

when you have time ping me , i would like to help solving CLJS-1473

[ClojureScript React Native] I took a stab at enumerating a roadmap with potential avenues of pursuit. Feedback welcome: http://cljsrn.org/roadmap.html

cljs-devtools 0.4.0 is out: https://github.com/binaryage/cljs-devtools/releases/tag/v0.4.0, someone posted it on HN a few days ago https://news.ycombinator.com/item?id=10400800, and it got 100+ upvotes, so I decided to do a new release

kewl

cljs-devtools is the best thing since sliced bread, really

Can't imagine writing cljs without it

I want a boot task that just injects it into my build! (please ☺️)

@martinklepsch: I’m thinking about packaging it as pre-compiled js extern dependency, something you would put into index.html before you include your app entry point, current devtools/install! way of installing it can be too late, the order of requires is not guaranteed and some code might run when requiring other dependencies. Would that work for you?

@dnolen: How did the training go?

I’m not familiar with boot much...

@cfleming: went great! Cursive and Figwheel both worked pretty well

Awesome, great news

much smoother than when we tried with Light Table (though to be expected for the obvious reasons, IntelliJ is mature commercial product)

Yeah, no doubt

@darwin: I think it used to not be guarannteed, but I thought there was a fix for that recently

Once I get a standalone IDE it should be a no-brainer

@cfleming: yeah we had to save all the IDE settings so that people got REPLs w/o config, that was kind of annoying

and it didn’t work consistently

At least I remember this being reported here and I think a fix was also done, but that's probably way behind the search fold

@jaen: typically you call devtools/install! somewhere in your main entry file (main.cljs) and there are some dependencies, all top-level code from those deps will run before top-level code in main.cljs. That’s something which is not obvious. And trying to put devtools/install! into first dependency which has no other dependencies didn’t work reliably. Order of deps wasn’t guaranteed as appears in the source file.

I’m glad to hear if that’s fixed.

Unless my memory is playing tricks on me of course

I have a feeling that pre-compiled js file with devtools included before your :main js file would work. I’m just afraid of differences between cljs versions. Imagine someone includes old pre-compiled clsj-devtools with latest app code or vice versa.

@darwin: boot-cljs allows you to inject require’s and init functions to the development shim which is a very useful approach, keeping the complexity of managing development stuff out of your actual application. This won’t fix any inherent loading issues of course. Just thought might be interesting for you

@martinklepsch: just reading it, you mean :init-fns here https://github.com/adzerk-oss/boot-cljs#options, right? this will be pretty elegant solution, but as you wrote, it won’t solve guaranteed require order in the main file (if the issue is still there)

I would need some magic, which would tell cljs-compiler to add particular require to all files, that would guarentee my code runs first, then all else

@darwin: yes. :init-fn and :requires are part of build specifications and can be modified by tasks in the build pipeline

@darwin I think your thing just needs to run after core but before everything else

we already have that problem for a couple things now

right

yeah so this problem already exists for the constants table (under advanced) and the bootstrapped macros

I can imagine it could bring more problems like 'if you have multiple things which need to run first, how do you specify their order'

well whatever we would do we wouldn’t support that

but perhaps worth pondering the very restricted useful case

it is not that big problem for cljs-devtools, in the bad case, user does not see formatted values but just plain js output the old-way

FWIW I already do this in shadow-build. Add a require to all files, that file does "runtime-setup" (eg. call (enable-console-print!)) so you don't have to do it in any of your namespaces

it is just annoyance, and puzzling if you don’t exactly understand that your code ran before cljs-devtools install!

obviously does something else for node thus "runtime setup" 😉

would be pretty straightforword to do this for another ns as well

but that doesn't help the general population not using shadow-build 😉

@thheller: thanks for the info, yep there is no drop-in oneliner solution

actually in plastic I solved it by using goog.require directly. My :main namespace contains only dependency to cljs-devtools and a call to devtools/install! and in index.html after including the main :main js file I call something like goog.require("plastic.main”)

that breaks my rule of not changing any HTML when switching between dev/prod 😛

oh wait you do it in the js file, thats fine

but it relies on the fact that cljs compiler compiles all namespaces in :optimizations :none mode, not only those required from :main entry point

AFAIK

hmm I just inject another :main for dev builds, but I think CLJS only allows one :main

wait, good point, if cljs compiler supported ordered list of :main entry points and did goog.require on them in order, that would solve it

yeah ... my recommendation on that point was ignored unfortunately

I volunteer to implement it on compiler side, if there was an agreement and no major obstacles

http://dev.clojure.org/jira/browse/CLJS-851?focusedCommentId=35629&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-35629

this issue has a whole lot of discussion about that stuff

looks like a can of worms… 😲

basically nothing I recommended went in ... but I blame only me for not communicating clearly 😞

@thheller: just finished reading the thread, you made really good points there, now I understand a bit more, having collection support for :main would be great, but I can help myself knowing this: In dev mode I might not use :main at all and just goog.require stuff in order I want.

@darwin: most of it was motivated by closure modules, which was the original feature I created shadow-build for which doesn't work without :main but I can see your point of wanting things a bit more flexible