Clojurians
#cljs-dev
<
2016-03-18
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

dnolen12:03:39

@domkm Maria Geller did a series of blogposts during Google Summer of Code - would be useful for someone to convert that into information on the wiki if that hasn’t already been done.

domkm15:03:04

@dnolen: Thanks, I'll take a look.

dnolen17:03:28

unless there are objections I'm planning on doing a release today, it’s been a couple of months now

richiardiandrea18:03:16

from a first bump in replumb I have the following warnings in the tests:

WARNING: Unknown compiler option ':ups-libs'.
WARNING: Unknown compiler option ':ups-foreign-libs'.
WARNING: Unknown compiler option ':ups-externs'.
WARNING: Unknown compiler option ':emit-constants'.

richiardiandrea18:03:22

Our require + source suite pass, I have just some inconsistency for the cache suite but I might need some update on my side

richiardiandrea18:03:45

I have to say that if require tests pass it is already really good :simple_smile:

dnolen18:03:17

@richiardiandrea: thanks for the feedback, yeah it looks like those options slipped through

dnolen18:03:22

minor thing, fixing now

dnolen18:03:14

fixed in master

nberger19:03:29

@dnolen :warning-handlers seems to be missing too

dnolen19:03:39

@nberger: k thanks

nberger19:03:56

thank you :simple_smile:

dnolen19:03:49

@nberger: fixed in master

nberger19:03:58

awesome, thanks

nberger19:03:10

and the good thing is that warning-handlers are not called for this warning. Was going to be fun if my warning-handlers made the build to fail because of a warning due to unrecognized warning-handlers option :simple_smile:

dnolen23:03:25

@bhauman: it seems Figwheel may include it’s own options in the compiler options? https://groups.google.com/d/msg/clojure/J2d_WNHrDr4/-vHm-XrlDQAJ

dnolen23:03:44

not a huge deal but will need to think about how @mfikes new nice warning on unsupported options interacts with that

mfikes23:03:37

Ahh… wow. Yeah… dang. The stuff I added presumed a known set of options.

dnolen23:03:00

@mfikes: we may want to just drop that part and look for mispellings?

mfikes23:03:11

@dnolen: Yes, I was thinking the same.

dnolen23:03:07

@mfikes: it’s not a big deal

dnolen23:03:16

warning handlers aren’t hooked in at this point - so it won’t fail builds

dnolen23:03:24

we can cut a release next Friday with the fix

mfikes23:03:51

It would be nice to understand the bigger picture. Perhaps—in the future—downstream tools could coalesce all of their tooling-specific compiler options under a single known key for this purpose. (Or somesuch.)

dnolen23:03:18

not a bad idea but would require some coordination