Fork me on GitHub
#clojurescript
<
2016-05-29
>
adambros02:05:39

at the risk of sounding ignorant, how do i use the latest code locally? interested in trying out cljs.spec myself dnolen 😎

dnolen02:05:17

@adambros: clone ClojureScript, ./script/bootstrap; ./script/build

dnolen02:05:24

you will need Maven installed

adambros02:05:49

thanks ill try that happy birthday as well 🍰

dnolen02:05:51

but brew install maven wil cover you on OS X at least

adambros03:05:51

yatta! it works, time to play! cljs parrot

debug03:05:32

Any good HTTP libraries as an alternative to cljs.ajax?

mfikes03:05:04

If anyone is interested in messing with cljs.spec via bootstrap on OS X, prebuilt Planck binary and instructions is at https://gist.github.com/mfikes/4b41b7c406c57228489b5edfb6ffe6a7

mfikes03:05:24

@debug There is also a #C0E1SN0NM channel with devs familiar with mobile devices

debug03:05:50

I reported this there too

debug03:05:23

This seems to be an Android only issue which I'd like to try with other libraries, if available

debug03:05:22

Any preferred direct ways to make network calls?

gadfly36106:05:15

Hey all, here is a list of TodoMVC implementations in clojurescript, please add to it if you know of others! https://github.com/gadfly361/cljs-todomvc

bronsa12:05:28

@dnolen: any reason why the ns name is cljs.spec rather than clojure.spec?

dnolen12:05:56

@bronsa for the simple reason that Clojure already used it

bronsa12:05:21

all the other namespaces (`.string`, .walk, .set ..) are prefixed clojure.

dnolen12:05:29

they don’t have macros

bronsa12:05:32

I'm confused as to what having or not having macros has to do with namespace name? is it a bootstrapping thing?

dnolen12:05:00

Clojure already used the name

bronsa12:05:16

that sucks

dnolen12:05:18

it’s about not knowing what to load

bronsa12:05:25

yeah I get it now

dnolen12:05:23

it might be worth just rewriting clojure.spec to cljs.spec but I need to think about it. Other option is to get clojure.spec to be written in .cljc

bronsa12:05:19

aliasing cljs.* to clojure.* would be another option (we already do that for cljs.core)

bronsa12:05:30

I always regret having namespaced cljs.tools.reader

dnolen12:05:38

@bronsa: yeah, that’s what I was suggesting ^

bronsa12:05:20

thought you were just suggesting it for cljs.spec in particular, but it might be worth for all of the cljs.* namespaces

dnolen12:05:51

@bronsa if we do it for cljs.spec I think it should be considered for all core nses

dnolen12:05:00

(wasn’t clear about that)

bronsa12:05:24

(`cljs.core.async` is another one)

risto12:05:03

What's the eta for the next release? is Schema or Herbert ClojureScript compatible?

dnolen12:05:26

@risto probably Friday this week. Schema is, don’t know about Herbert.

nathanmarz12:05:42

@dnolen took your advice on doing dynamic calls to def for the inline caching for specter in cljs – works great

nathanmarz12:05:11

@dnolen one question, to avoid "Use of undeclared Var" warnings, is reading the var by using a symbol like "user.pathcache1234" ok to do?

dnolen12:05:26

if you are generating some symbol you want the compiler to not warn about (since you have some information the compiler does not that it will in fact exist)

nathanmarz12:05:56

oh awesome, I'll try that instead

nathanmarz12:05:12

was browsing the cljs codebase yesterday looking for something exactly like that 🙂

maxp12:05:46

звони

anmonteiro14:05:49

correct me if I’m wrong, but there’s no way to conditionally require a namespace in CLJS, right?

anmonteiro14:05:14

I’d need to have different builds or something to solve that problem, AFAICT

anmonteiro14:05:41

example use case is I only want to require my NS which has cljs.spec specs if the CLJS version is >= 1.9

dnolen14:05:29

@anmonteiro: yes not possible, earlier versions of reader conditional could have supported that

adamfrey22:05:20

how can I figure out why two values are fail an equality = check in CLJS?

adamfrey22:05:54

that question might seem a little crazy. I may be able to give more context in a sec

adamfrey22:05:25

I figured out my problem. I had two vectors with mutable Javascript objects in them. The objects printed the same but weren’t equal, so my vectors weren’t equal