Re: Possible ClojureScript compiler issue...

This issue is fixed in master now thanks to Thomas Heller. The performance hit is negligible. Thank you for the report. David On Tue, Oct 18, 2016 at 3:45 PM, John Szakmeister wrote: > On Tue, Oct 18, 2016 at 5:59 AM, Thomas Heller > wrote: > >

Re: Possible ClojureScript compiler issue...

On Tue, Oct 18, 2016 at 5:59 AM, Thomas Heller wrote: > Don't think there is a best practice for your case in particular. Okay. Earlier in the thread you said "while this issue can be very confusing you will hardly ever run into it when following best practices." So it

Re: Possible ClojureScript compiler issue...

Just a quick glance makes it look like handlers can be overridden, but I haven't tried this and I don't think it's documented anywhere: https://github.com/cognitect/transit-cljs/blob/master/src/cognitect/transit.cljs#L109 On Tue, Oct 18, 2016 at 11:41 AM John Szakmeister

Re: Possible ClojureScript compiler issue...

Yes, you could do that, but it could also do Bad Things. Namely if you have strings that match some of the format, it could be misinterpreted as Transit data rather than JSON, so I don't consider it a particularly useful solution either. It just moves where the problem can happen. :-( If there

Re: Guidelines/Recommendations for namespaces and qualified keywords

On Saturday, October 15, 2016 at 10:17:15 PM UTC-5, Josh Tilles wrote: > > I’ve got a couple questions for Alex Miller and/or the other Cognitect > folks. > >1. *Are single-segment namespaces still “bad” when it comes to >registering specs under qualified keywords?* > > I will give

Re: join* tables from csv

You may also like this answer using DataScript to solve a similar problem: http://stackoverflow.com/questions/39712460/how-to-map-different-values-from-2-sets-in-clojure-based-on-unique-value/39714081#39714081 On Tue, Oct 18, 2016 at 6:09 AM, Moe Aboulkheir wrote: > (defn

Re: join* tables from csv

(defn join* [d1 c1 d2 c2] (clojure.set/join (into #{} d1) (into #{} d2) {c1 c2})) Or else look at the implementation of set/join. Take care, Moe On Tue, Oct 18, 2016 at 9:41 AM, wrote: > Hey guys, i'm beginner and need help. > > I have a task: > > ;; (join*

join* tables from csv

Hey guys, i'm beginner and need help. I have a task: ;; (join* (join* student-subject :student_id student :id) :subject_id subject :id) ;; => [{:subject "Math", :subject_id 1, :surname "Ivanov", :year 1998, :student_id 1, :id 1} ;; {:subject "Math", :subject_id 1, :surname "Petrov", :year

Re: Possible ClojureScript compiler issue...

If you're parsing raw json streams/strings, I think transit claims to be a 30x perf improvement over js/JSON.parse+js->clj: http://swannodette.github.io/2014/07/26/transit-clojurescript On Tue, Oct 18, 2016 at 6:41 AM Matching Socks wrote: > A reliable "implements?" would

Re: Possible ClojureScript compiler issue...

A reliable "implements?" would be better than a fast-and-sometimes-wrong "implements?". With that in mind, have you tried a distinct sentinel object, as opposed to true? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group,

Re: Possible ClojureScript compiler issue...

Don't think there is a best practice for your case in particular. The issue is that js->cli is built on top of protocols to allow converting custom JS types to CLJS types. Which makes it extensible for the price of checking protocols. In your case you are converting JSON which cannot have

Re: complex made simple?

1. Use Yoneda Lemma. Its intuitive explanation is: You work at a particle accelerator. You want to understand some particle. All you can do are throw other particles at it and see what happens. If you understand how your mystery particle responds to all possible test particles at all possible test

Re: Possible ClojureScript compiler issue...

On Tue, Oct 18, 2016 at 2:59 AM, Thomas Heller wrote: [snip] > While this issue can be very confusing you will hardly ever run into it when > following best practices. As David suggested using a custom js->clj here > would prevent the issue and is probably the best course of

Re: Help with using spec

Hi Alex, Thanks very much for this, makes sense and has solved my issue. After a trying a few things, it appears that the ArityException was thrown because I would have needed to wrap my regex with s/spec i,e, (s/fdef my-function :args (s/cat :board (s/spec ::board))) So I think this all

Re: [ANN] clj-xchart – A charting/plotting library for Clojure

Hi Marshall, You might want to have a look at https://github.com/aphyr/gnuplot >From the repo: "Datasets are streamed as sequences directly to gnuplot's stdin, so there's no temporary files to worry about. Yep, lazy sequences are streamed lazily. My laptop can plot about 10 million points in

Re: Possible ClojureScript compiler issue...

Yeah the issue can be quite confusing since the error produced may complain about protocols you are not even calling anywhere. I've run into it several times when the code ended up checking protocols on js/window. Since that has all the munged global variables closure produces just about