Re: Sum types in Clojure? Better to represent as tagged records or as variant vectors?

I'm late to this party, and maybe this discussion has already gone on too long. If so, I'm sorry for dredging it back up. But I'm curious about where Tim was going with this, because I feel like I might be missing out on a great idea: On Tuesday, August 29, 2017 at 9:12:33 AM UTC-5, Tim

Re: [ANN] JMH-Clojure: Seamless JMH benchmarking for Clojure

This looks really fantastic - thank you! I've used JMH recently and it's definitely awkward to use - I'll use this next time for sure. On 29 September 2017 at 09:24, wrote: > A data-oriented API to JMH > , the Java >

[ANN] JMH-Clojure: Seamless JMH benchmarking for Clojure

A data-oriented API to JMH , the Java Microbenchmark Harness. Much more information is available at the github page: https://github.com/jgpc42/jmh-clojure -- You received this message because you are subscribed to the Google Groups "Clojure"

Re: Help ship Clojure 1.9!

And to be clear, it doesn't only affect people who try to use ##Inf or ##NaN in their Clojurescript code. It affects all existing Clojurescript code, because running the Clojurescript compiler in a new version of Clojure causes all Clojurescript code to emit these ## characters directly into the

Re: Help ship Clojure 1.9!

On Thu, Sep 28, 2017 at 11:02 AM, Jeaye wrote: > This has been the only issue we've run into with 1.9.0-beta1 ( ticket is > here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end, > all tests are good, but we can't currently use beta1 (or alpha20) on the >

Re: Help ship Clojure 1.9!

Clojure 1.9 has been great for me so far. I think it's worth considering the problem Luke brought up regarding the REPL caught handler [1], especially since the compiler now checks macro specs. Having a slightly better knob for that might be nice, since it's an integration point. (This is not

Re: Help ship Clojure 1.9!

This has been the only issue we've run into with 1.9.0-beta1 ( ticket is here https://dev.clojure.org/jira/browse/CLJS-2352 ). On our back-end, all tests are good, but we can't currently use beta1 (or alpha20) on the front-end, since this issue causes CLJS to choke. I'm hoping that a new

Re: Help ship Clojure 1.9!

Thanks Beau! On Thu, Sep 28, 2017 at 1:06 PM, Beau Fabry wrote: > Identified an issue with prismatic/schema https:// > github.com/plumatic/schema/pull/399 > > On Thursday, September 28, 2017 at 9:18:52 AM UTC-7, Nathan Fisher wrote: >> >> Hi Stuart, >> >> Looks like any

Re: Help ship Clojure 1.9!

Identified an issue with prismatic/schema https://github.com/plumatic/schema/pull/399 On Thursday, September 28, 2017 at 9:18:52 AM UTC-7, Nathan Fisher wrote: > > Hi Stuart, > > Looks like any project using lein-cljsbuild will be affected. > > I forked and bumped the Clojure and ClojureScript

Re: Help ship Clojure 1.9!

Hi Stuart, Looks like any project using lein-cljsbuild will be affected. I forked and bumped the Clojure and ClojureScript version to latest and got the same error with their simple project: See Commit: https://github.com/nfisher/lein-cljsbuild/commit/5df5d3c5bb447b51a75abbbccdc72447814883a0

Re: Help ship Clojure 1.9!

Hi Nathan, I suspect that is the same as https://github.com/clojure/clojurescript/commit/89914d2ead964122f99e638edda0cd96d330cb66. I don't have a sense of how many CLJS project this is going to cascade into, or what all will be needed. Anyone? Stu On Thu, Sep 28, 2017 at 10:44 AM, Nathan Fisher

Re: Help ship Clojure 1.9!

Hi Stuart, Working to create a minimal test case but upgrading from alpha19 to beta1 seems to have broken lein-cljsbuild. I get the following error: >> snip >> *SEVERE: /Users/nathanfisher/workspace/mklpq/target/cljsbuild-compiler-0/cljs/core.js:3579: ERROR - Parse error. primary

Help ship Clojure 1.9!

Clojure 1.9 has been quite stable throughout the alpha period, and we now hope to release after a very short beta. Please test your existing programs on the latest beta (see below), and respond on this thread ASAP if you discover anything you believe to be a regression. Thanks! Stu ;; Clojure

Re: read-line is limited to 4095 chars

On Tuesday, 26 September 2017 12:28:26 UTC+1, baptiste...@oscaro.com wrote: > > I was using read-line to read a large line and found it limits its input > to 4095 chars. I tested this on both Clojure 1.8.0 and 1.9.0-beta1. > > I tested this on Windows. I found that piping from the CMD.EXE