[ClojureScript] Re: [ANN] Longshi a ClojureScript port of Fressian

[Alex Miller]

Cool stuff Peter. It would be interesting to compare performance with 
transit-cljs https://github.com/cognitect/transit-cljs. Transit has the same 
caching and extensibility benefits of Fressian but leverages the very fast 
JavaScript parser capabilities built into the browser, so is likely faster.

Alex

On Friday, August 1, 2014 3:33:58 PM UTC-5, pe...@bendyworks.com wrote:
 I'm happy to announce a port of Fressian to ClojureScript.
 
 The public api mirrors data.fressian api with a few exceptions.  Records 
 don't have a generic writer but you can easily append the handlers with the 
 write-record function.  There is no inheritance lookup for types so every 
 different type will need it's own handler.  The tagged helper functions 
 (tagged-object?, tag, tagged-value) are not included.
 
 I see the use case for Fressian in ClojureScript streaming large amounts of 
 data that has significant structural similarity.  Fressian caching 
 capabilities allow large values to be represented as a single integer in the 
 bytestream.  
 
 This is my first large ClojureScript library so any suggestions for 
 improvements are welcome.
 
 Thanks to Bendyworks for letting me develop this during my work hours.
 
 Clojars Link: https://clojars.org/longshi
 Repo: https://github.com/spinningtopsofdoom/longshi
 
 Peter Schuck

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: [ANN] Longshi a ClojureScript port of Fressian

[Alex Miller]

I took significant structural similarity to primarily mean at least maps
with similar keys, which Transit caching will cover.


On Sat, Aug 2, 2014 at 1:49 PM, David Nolen dnolen.li...@gmail.com wrote:

 In Transit, maps keys, symbols, keywords, and tagged value tags are
 subject to caching.

 Fressian's caching strategy is far more flexible from what I
 understand. That said transit-cljs is 20-30X faster than
 cljs.reader/read-string on the benchmarks I've tried across various
 browser and command line JS environments.

 David

 On Sat, Aug 2, 2014 at 2:26 PM, Sean Grove s...@bushi.do wrote:
  I thought transit's caching only applied to map keys? Pretty unclear on
 what
  Fressian's can do
 
 
  On Sat, Aug 2, 2014 at 8:23 AM, Alex Miller a...@puredanger.com wrote:
 
  Cool stuff Peter. It would be interesting to compare performance with
  transit-cljs https://github.com/cognitect/transit-cljs. Transit has
 the same
  caching and extensibility benefits of Fressian but leverages the very
 fast
  JavaScript parser capabilities built into the browser, so is likely
 faster.
 
  Alex
 
  On Friday, August 1, 2014 3:33:58 PM UTC-5, pe...@bendyworks.com wrote:
   I'm happy to announce a port of Fressian to ClojureScript.
  
   The public api mirrors data.fressian api with a few exceptions.
  Records
   don't have a generic writer but you can easily append the handlers
 with the
   write-record function.  There is no inheritance lookup for types so
 every
   different type will need it's own handler.  The tagged helper
 functions
   (tagged-object?, tag, tagged-value) are not included.
  
   I see the use case for Fressian in ClojureScript streaming large
 amounts
   of data that has significant structural similarity.  Fressian caching
   capabilities allow large values to be represented as a single integer
 in the
   bytestream.
  
   This is my first large ClojureScript library so any suggestions for
   improvements are welcome.
  
   Thanks to Bendyworks for letting me develop this during my work hours.
  
   Clojars Link: https://clojars.org/longshi
   Repo: https://github.com/spinningtopsofdoom/longshi
  
   Peter Schuck
 
  --
  Note that posts from new members are moderated - please be patient with
  your first post.
  ---
  You received this message because you are subscribed to the Google
 Groups
  ClojureScript group.
  To unsubscribe from this group and stop receiving emails from it, send
 an
  email to clojurescript+unsubscr...@googlegroups.com.
  To post to this group, send email to clojurescript@googlegroups.com.
  Visit this group at http://groups.google.com/group/clojurescript.
 
 
  --
  Note that posts from new members are moderated - please be patient with
 your
  first post.
  ---
  You received this message because you are subscribed to the Google Groups
  ClojureScript group.
  To unsubscribe from this group and stop receiving emails from it, send an
  email to clojurescript+unsubscr...@googlegroups.com.
  To post to this group, send email to clojurescript@googlegroups.com.
  Visit this group at http://groups.google.com/group/clojurescript.

 --
 Note that posts from new members are moderated - please be patient with
 your first post.
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups ClojureScript group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojurescript/xhdrGunEXPE/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojurescript+unsubscr...@googlegroups.com.
 To post to this group, send email to clojurescript@googlegroups.com.
 Visit this group at http://groups.google.com/group/clojurescript.


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2301, Transducers!

[Alex Miller]

I will file an issue - thanks for the analysis!

Alex

On Saturday, August 9, 2014 8:41:34 AM UTC-5, Curtis Summers wrote:
 I think this may be a cache issue with the central repo.  I can both see the 
 file via browsing and they are in the index for me, but the actual jar file 
 brings up a 404:
 
 http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/clojurescript-0.0-2307.jar
 
 However, appending a junk query string on the url correctly downloads the jar:
 
 http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/clojurescript-0.0-2307.jar?cache-is-broken
 
 It looks like this is being served up via varnish cache.  The jar url is 
 somehow cached as a 404.  Depending on your location and the various central 
 repo caches, you may be seeing different results (e.g., the index not listing 
 the versions).
 
 Anybody know who to contact at central repo?
 
 --Curtis
 
 
 On Saturday, August 9, 2014 6:00:47 AM UTC-5, Nicola Mometto wrote:
  I can confirm, there seem to be problem fetching clojurescript versions
  
  0.0-2301 and 0.0-2307.
  
  
  
  Browsing the Central repo the files are there:
  
  http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2301/
  
  http://repo1.maven.org/maven2/org/clojure/clojurescript/0.0-2307/
  
  
  
  But the maven-metadata.xml file hasn't indexed them:
  
  http://repo1.maven.org/maven2/org/clojure/clojurescript/maven-metadata.xml
  
  
  
  
  
  Frank Versnel writes:
  
  
  
   Hi David,
  
  
  
   Leiningen couldn't find this version on clojars/maven central. Any other 
   repository I might need to add to get access to super early clojurescript 
   builds?
  
  
  
   Cheers,
  
   Frank

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: ANN: ClojureScript 0.0-2301, Transducers!

[Alex Miller]

Sonatype reports the cache has been purged and it should be working again.
Seems to be for me.


On Mon, Aug 11, 2014 at 8:35 AM, Ivan Mikushin i.mikus...@gmail.com wrote:

 The same issue (and workaround) applies to clojurescript-0.0.2311

 --
 Note that posts from new members are moderated - please be patient with
 your first post.
 ---
 You received this message because you are subscribed to a topic in the
 Google Groups ClojureScript group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/clojurescript/ghpbnZKjx3w/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 clojurescript+unsubscr...@googlegroups.com.
 To post to this group, send email to clojurescript@googlegroups.com.
 Visit this group at http://groups.google.com/group/clojurescript.


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: ANN: State of Clojure 2014 Survey - please contribute!!

[Alex Miller]

I'd be happy to include these for consideration next year. I think on the 
dev env we have removed some like this because they were not well 
represented in the results. The landscape for dev envs changes 
significantly year to year.

On Wednesday, October 8, 2014 11:32:53 PM UTC-5, Mars0i wrote:

 Thanks for the survey!

 I have a couple of suggestions/questions:

 For domains, there are no categories for scientific or other research 
 applications.  For example, I mainly use Clojure for writing agent-based 
 models for academic research.  Would a set of categories in this area be 
 usedful?

 The development environment options leave out more basic, simple methods.  
 For example, I generally use vim and a repl run from the command line, 
 which works well for me.  I guess I should chose other, but that means I 
 don't get counted among the vim users.  Maybe the number of people like me 
 is so small as to be ignorable?


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] 2014 State of Clojure ClojureScript Survey ends Oct 17th

[Alex Miller]

I hope to have something including the raw results published early this week 
but depends how long it takes to make a report.

Alex

On Sunday, October 19, 2014 5:47:21 AM UTC-5, Gary Verhaegen wrote:
 Yes, they do. Probably within two weeks from now, according to the original 
 announcement. No hard deadline though.
 
 On Sunday, 19 October 2014, Yehonathan Sharvit vie...@gmail.com wrote:
 On Tuesday, 14 October 2014 16:21:13 UTC+3, Alex Miller  wrote:
 
  Just a reminder that this Friday is the last day to complete the 2014 State 
  of Clojure  ClojureScript surveys:
 
 
 
 
 
  http://blog.cognitect.com/blog/2014/10/3/2014-state-of-clojure-clojurescript-survey
 
 
 
 
 
 
 
  So far 1110 people have filled out the State of Clojure survey and 544 
  people have filled out the State of ClojureScript. If you haven't filled 
  out the surveys yet, we would love for your answers to be included. The raw 
  data and some analysis will be posted next week.
 
 
 
 
 
  Alex
 
 
 
 Do you intend to publish the resutls?
 
 
 
 --
 
 Note that posts from new members are moderated - please be patient with your 
 first post.
 
 ---
 
 You received this message because you are subscribed to the Google Groups 
 ClojureScript group.
 
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to clojurescript+unsubscr...@googlegroups.com.
 
 To post to this group, send email to clojurescript@googlegroups.com.
 
 Visit this group at http://groups.google.com/group/clojurescript.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] State of Clojure/ClojureScript 2014 survey results

[Alex Miller]

I've published links to the State of Clojure and ClojureScript 2014 survey
results here:
http://blog.cognitect.com/blog/2014/10/20/results-of-2014-state-of-clojure-and-clojurescript-survey

That page links to some reports with graphs where you can also export the
raw data. I also have links to broken out answers from each of the open
text questions for easier consumption. Those are redundant, but perhaps
useful.

I have not had the time to do any analysis or commentary on these yet. Of
particular interest in a few questions are comparisons with prior years
which are also linked from the post.

Big thanks to everyone that participated - it's invaluable to get this
snapshot of the community every year, especially as we grow.

Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: State of Clojure/ClojureScript 2014 survey results

[Alex Miller]

Thanks, I do hope to follow up with some analysis, just thought it was more 
important to release the data sooner rather than later.

Alex

On Thursday, October 23, 2014 12:30:47 PM UTC-5, Fergal Byrne wrote:

 Great stuff Alex. I'd recommend taking a look at this talk 
 https://www.youtube.com/watch?v=3MvKLOecT1I which does a great analysis 
 job on a similar survey for Erlang. 

 On Thu, Oct 23, 2014 at 4:58 PM, Alex Miller al...@puredanger.com 
 javascript: wrote:

 I've published links to the State of Clojure and ClojureScript 2014 
 survey results here:

 http://blog.cognitect.com/blog/2014/10/20/results-of-2014-state-of-clojure-and-clojurescript-survey

 That page links to some reports with graphs where you can also export the 
 raw data. I also have links to broken out answers from each of the open 
 text questions for easier consumption. Those are redundant, but perhaps 
 useful. 

 I have not had the time to do any analysis or commentary on these yet. Of 
 particular interest in a few questions are comparisons with prior years 
 which are also linked from the post.

 Big thanks to everyone that participated - it's invaluable to get this 
 snapshot of the community every year, especially as we grow.

 Alex


  -- 
 You received this message because you are subscribed to the Google
 Groups Clojure group.
 To post to this group, send email to clo...@googlegroups.com 
 javascript:
 Note that posts from new members are moderated - please be patient with 
 your first post.
 To unsubscribe from this group, send email to
 clojure+u...@googlegroups.com javascript:
 For more options, visit this group at
 http://groups.google.com/group/clojure?hl=en
 --- 
 You received this message because you are subscribed to the Google Groups 
 Clojure group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to clojure+u...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




 -- 

 Fergal Byrne, Brenter IT

 http://inbits.com - Better Living through Thoughtful Technology
 http://ie.linkedin.com/in/fergbyrne/ - https://github.com/fergalbyrne

 Founder of Clortex: HTM in Clojure - 
 https://github.com/nupic-community/clortex

 Author, Real Machine Intelligence with Clortex and NuPIC 
 Read for free or buy the book at https://leanpub.com/realsmartmachines

 Speaking on Clortex and HTM/CLA at euroClojure Krakow, June 2014: 
 http://euroclojure.com/2014/
 and at LambdaJam Chicago, July 2014: http://www.lambdajam.com

 e:fergalby...@gmail.com javascript: t:+353 83 4214179
 Join the quest for Machine Intelligence at http://numenta.org
 Formerly of Adnet edi...@adnet.ie javascript: http://www.adnet.ie
  

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure/West 2015 Call for Presentations

[Alex Miller]

Just to be clear, Clojure should be read in a big tent way here to include 
ClojureScript and anything Clojure-related of course. ClojureScript talks 
desired!!

Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure/West 2015 Call for Presentations

[Alex Miller]

Hello Clojure fans!

We will be returning to Portland (same theater as 2013) for Clojure/West
this year on April 20-22nd and workshops on the weekend prior. We currently
plan to have tickets on sale Monday - see http://twitter.com/clojurewest
and http://clojurewest.org for more info and last minute details.

However, the Call for Presentations is open now! We are accepting
submissions until Feb. 11th in the general areas of core language,
libraries, tools, experience reports, ideas, and fun (although it's all
pretty fun when it's Clojure right?).

https://cognitect.wufoo.com/forms/clojurewest-2015-call-for-presentations/

Speakers receive free admission, $550 stipend, and up to 4 room nights at
the conference hotel (Embassy Suites Downtown Portland). Sessions are 40
minutes long. Multiple submissions are allowed, although we'd prefer no
more than three. Beginner or foundational level talks are welcome!

If you are mulling over multiple ideas, need feedback, or just aren't sure
whether something is a good idea, please feel free to send an email to
eve...@cognitect.com and we will get back to you as soon as possible.

If your company is interested in sponsoring Clojure/West, please check out
the prospectus at http://clojurewest.org/sponsorship and let us know. We've
had an amazing initial response - thanks if you've already contacted us.

Also, we will be running an opportunity grant program again for
Clojure/West with travel grants and tickets for qualified applicants. More
to come in the next few weeks on that.

Hope to see everyone there!
Alex Miller and Lynn Grogan

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: Sizing The CLJS Community

[Alex Miller]

On Thursday, April 23, 2015 at 10:08:38 PM UTC-5, Mike Thompson wrote:
 I'm curious about the approximate size of the clojurescript community, and 
 its current trajectory numerically speaking.
 
 So, absolute numbers like:  how many active cljs programmers are there?  
 And/or relative numbers like: growing at X%. 
 
 I'm wondering where useful numbers might live. 
 
 Obviously there is google trends for relative numbers:
 https://www.google.com.au/trends/explore#q=cljs
 https://www.google.com.au/trends/explore#q=clojurescript
 
 
 I've also found one interesting absolute number via:
 https://clojars.org/lein-cljsbuild/versions/1.0.5
 
 There have been 5258 downloads of cljsbuild. This is a relatively recent 
 release (8 weeks ago) so most will have moved across to use it, and there 
 might not be too much duplication in that number because few will have 
 changed machines in that time or deleted their .m2 and re-downloaded. Maybe. 
 
 Of course, this number ignores boot. And there will still be some on 1.0.4. 
 Etc. 
 
 Other thoughts?
 
 
 --
 Mike


When I collected numbers for my 2014 Clojure/West talk (a year ago), I found 
there were about 10k people on the main Clojure mailing list and about 10k 
people combined across all Clojure meetup groups (iirc). So my estimate is that 
that is a min bar on size of the community. The yearly State of Clojure survey 
has reported about 50% of users using Clojure-only and 50% using 
Clojure+ClojureScript for the last several years running so I'm inclined to 
take that as the best estimates we have. 

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure 1.7.0-beta2

[Alex Miller]

Clojure 1.7.0-beta2 is now available.

Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-beta2/
- Leiningen: [org.clojure/clojure 1.7.0-beta2]

Regression fixes since 1.7.0-beta1:

1) CLJ-1711 - structmap iterator broken
2) CLJ-1709 - range wrong for step != 1
3) CLJ-1713 - range chunks are not serializable
4) CLJ-1698 - fix reader conditional bugs

Additional enhancements to new features since 1.7.0-beta1:

1) CLJ-1703 - Pretty print #error and new public function Throwable-map
2) CLJ-1700 - Reader conditionals now allowed in the REPL
3) CLJ-1699 - Allow data_readers.cljc as well as data_readers.clj

For a full list of changes since 1.6.0, see:
https://github.com/clojure/clojure/blob/master/changes.md

Please give it a try and let us know if things are working (or not)!

- Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure 1.7.0-beta2

[Alex Miller]

On Fri, May 1, 2015 at 2:53 PM, Nicola Mometto brobro...@gmail.com wrote:


 Now, if you want to argue that the compiler should immediately throw an
 error as soon as the wrong type hint is used rather than silently ignore
 it and fail when the type-hinted form is used, I'll agree with you and
 I've proposed to make the compiler stricter a number of times on the
 clojure-dev ML and talked about it on IRC but I guess either it's not a
 priority for the clojure/core team or they're simply not interested in
 more compile-time checks.


Is there a ticket?

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure 1.7.0-beta3

[Alex Miller]

Clojure 1.7.0-beta3 is now available.

Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-beta3/
- Leiningen: [org.clojure/clojure 1.7.0-beta3]

Additional enhancements to new features since 1.7.0-beta2:

1) CLJ-1728 - `source` fn now works for vars in cljc files
2) CLJ-1716 - the new print format for Throwables now includes ex-data
3) CLJ-1726 - restored IPending/realized? support for iterate and cycle
sequences to detect delayed computation

Regression and bug fixes since 1.7.0-beta2:

1) CLJ-1723 - expanding transducers (cat, mapcat) that produced nil values
would throw NPE
2) CLJ-1727 - new long-optimized range had bugs related to overflow
3) CLJ-1648 - use equals() instead of == when resolving Symbol in compiler
4) CLJ-1195 - deftype should expand to ns-qualified invocation of fn to
allow overrides (this issue was blocking Prismatic Schema via Plumbing
issue #74)

For a full list of changes since 1.6.0, see:
https://github.com/clojure/clojure/blob/master/changes.md

Please give it a try and let us know if things are working (or not)!

- Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure 1.7.0-beta1 released

[Alex Miller]

Well, we never added fancy printing, just data printing of Throwables. :) 
 

But we were working on this in the context of another thing that got moved 
out and I have pulled that back as a separate ticket:
http://dev.clojure.org/jira/browse/CLJ-1703

Haven't talked to Rich about it yet, but we'll discuss for 1.7.


On Tuesday, April 14, 2015 at 6:06:49 AM UTC-5, Geraldo Lopes de Souza 
wrote:

 Hi, 


 Fancy printing is not working.

 Geraldo 


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: [ANN] Clojure 1.7.0-beta1 released

[Alex Miller]

There is a ticket to consider a portable solution to this issue:

http://dev.clojure.org/jira/browse/CLJ-1293

On Monday, April 13, 2015 at 5:45:35 AM UTC-5, David Nolen wrote:

 The only reason :default exists is because *anything* in JavaScript can be 
 thrown and there needs to be some way to catch non-Error derived values. 
 This is not the case for Java of course. :default could probably be aliased 
 to Throwable, but in the meantime differences like this are now handleable 
 via conditional reading.

 David

 On Mon, Apr 13, 2015 at 6:37 AM, Robin Heggelund Hansen 
 skinn...@gmail.com javascript: wrote:

 Hmm... In Clojurescript you can do the following

 (try
   ;; throw something
   (catch :default e
  e))

 When I try the same thing in Clojure, it seems to not be supported. Is 
 there any plans to support this syntax in Clojure 1.7?




-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure 1.7.0-beta1 released

[Alex Miller]

I think what you're seeing here makes sense.

On Sunday, April 12, 2015 at 3:39:15 PM UTC-5, whodidthis wrote:

 Are there any thoughts on code like this:

 #_


This says to ignore the next read form
 

 #?(:cljs (def unrelated-1 nil))


This evaluates to *nothing*, ie nothing is read, so it is not ignored by 
the #_.
 

 #?(:cljs (def unrelated-2 nil))
 #?(:cljs (def unrelated-3 nil))


These also read as *nothing*.
 

 #?(:clj (def n 10))


This *is* read, but ignored per the prior #_ 

#?(:clj (defn num [] n))
 ; compile on clj =RuntimeException: Unable to resolve symbol: n


And then this makes sense.
 


 I guess it's fine if it continues to work that way but I can imagine it 
 being a little surprising from time to time heh


Conditional reading is definitely something to be careful about - I think 
in this case you are combining two types of conditional reading so be 
doubly careful. :) 

To get the effect you want in this, using #_ *inside* the reader 
conditional would work:

#?(:cljs #_(def unrelated-1 nil))

 

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

Re: [ClojureScript] [ANN] Clojure 1.7.0-RC1 now available

[Alex Miller]

Thanks David! Hopefully we'll have an RC2 out soon.

On Friday, June 12, 2015 at 5:19:28 AM UTC-5, David Della Costa wrote:
 Alex, I'm behind the curve but here's another experience report:
 
 We've been testing with RC1 for the last few weeks in a development
 branch, and found nothing out of the ordinary.  This is a relatively
 substantial web app using libs such as compojure, clojure.java.jdbc,
 Prismatic's schema, and a bunch of other fairly common libraries.
 
 The only thing that I've really noticed, in fact, is that it's lovely to
 get rid of CLJX and have reader conditionals baked-in!
 
 Thanks--
 
 DD

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure 1.7.0-RC1 now available

[Alex Miller]

No, please report if so.

On Tuesday, May 26, 2015 at 8:39:32 PM UTC-5, Julien wrote:

 I just ported an app with significant CLJX usage (55 files) to reader 
 conditionals and it works perfectly!

 It looks like there is a small issue related to map literal containing 
 comments but I am not sure if it has been reported yet.

 Julien


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure 1.7.0-RC1 now available

[Alex Miller]

Clojure 1.7.0-RC1 is now available.

Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-RC1/
- Leiningen: [org.clojure/clojure 1.7.0-RC1]

The only change since 1.7.0-beta3 is CLJ-1706, which makes reader
conditional splicing an error at the top level (previously it would
silently drop all but the first spliced element).

For a full list of changes since 1.6.0, see:
https://github.com/clojure/clojure/blob/master/changes.md

Please give it a try and let us know if things are working (or not). The
more and quicker feedback we get, the sooner we can release 1.7.0 final!

- Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] Re: [ANN] Clojure 1.7.0-RC1 now available

[Alex Miller]

In what way is it broken? Both before and after wrapped a mutable iterator into 
a caching seq. The new one is different in that it chunks so reads 32 at a time 
instead of 1. However combining either with other chunking sequence operations 
would have the same effect which is to say that using that mutable iterator 
with anything else, or having expectations about its rate of consumption was as 
dubious before as it is now.

Unless of course I misunderstand your intent, which possible because I am on a 
phone without easy access to look further at the commit and am going by memory.



 On May 26, 2015, at 2:17 PM, Marshall Bockrath-Vandegrift llas...@gmail.com 
 wrote:
 
 Some of my code is broken by commit c47e1bbcfa227723df28d1c9e0a6df2bcb0fecc1, 
 which landed in 1.7.0-alpha6 (I lasted tested with -alpha5 and have been 
 unfortunately busy since).  The culprit is the switch to producing seqs over 
 iterators as chunked iterators.  This would appear to break seq-based 
 traversal of any iterator implementing the not-uncommon Java pattern of 
 mutating and re-yielding the same object on each `next()` invocation.
 
 I'm unable to find an existing ticket for this apparent-regression.  Should I 
 create one, or did I miss the existing ticket, or is there some mitigating 
 issue which makes this a non-problem?
 
 Thanks.
 
 -Marshall
 
 On Thu, May 21, 2015 at 12:31 PM Alex Miller a...@puredanger.com wrote:
 Clojure 1.7.0-RC1 is now available.
 
 Try it via
 - Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0-RC1/
 - Leiningen: [org.clojure/clojure 1.7.0-RC1]
 
 The only change since 1.7.0-beta3 is CLJ-1706, which makes reader 
 conditional splicing an error at the top level (previously it would silently 
 drop all but the first spliced element).
 
 For a full list of changes since 1.6.0, see:
 https://github.com/clojure/clojure/blob/master/changes.md
 
 Please give it a try and let us know if things are working (or not). The 
 more and quicker feedback we get, the sooner we can release 1.7.0 final!
 
 - Alex
 -- 
 You received this message because you are subscribed to the Google Groups 
 Clojure Dev group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to clojure-dev+unsubscr...@googlegroups.com.
 To post to this group, send email to clojure-...@googlegroups.com.
 Visit this group at http://groups.google.com/group/clojure-dev.
 For more options, visit https://groups.google.com/d/optout.
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Clojure Dev group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to clojure-dev+unsubscr...@googlegroups.com.
 To post to this group, send email to clojure-...@googlegroups.com.
 Visit this group at http://groups.google.com/group/clojure-dev.
 For more options, visit https://groups.google.com/d/optout.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure 1.7.0 is now available

[Alex Miller]

We are pleased to announce the release of Clojure 1.7.

- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.7.0/
- Leiningen: [org.clojure/clojure 1.7.0]

The two headline features for 1.7 are transducers and reader conditionals.
Also see the complete list (
https://github.com/clojure/clojure/blob/master/changes.md) of all changes
since Clojure 1.6 for more details.

## Transducers

Transducers (http://clojure.org/transducers) are composable algorithmic
transformations. They are independent from the context of their input and
output sources and specify only the essence of the transformation in terms
of an individual element. Because transducers are decoupled from input or
output sources, they can be used in many different processes - collections,
streams, channels, observables, etc. Transducers compose directly, without
awareness of input or creation of intermediate aggregates.

Many existing sequence functions now have a new arity (one fewer argument
than before). This arity will return a transducer that represents the same
logic but is independent of lazy sequence processing. Functions included
are: map, mapcat, filter, remove, take, take-while, drop, drop-while,
take-nth, replace, partition-by, partition-all, keep, keep-indexed,
map-indexed, distinct, and interpose. Additionally some new transducer
functions have been added: cat, dedupe, and random-sample.

Transducers can be used in several new or existing contexts:

* into - to collect the results of applying a transducer
* sequence - to incrementally compute the result of a transducer
* transduce - to immediately compute the result of a transducer
* eduction - to delay computation and recompute each time
* core.async - to apply a transducer while values traverse a channel

## Portable Clojure and Reader Conditionals

It is now common to see a library or application targeting multiple Clojure
platforms with a single codebase. Clojure 1.7 introduces a new extension
(.cljc) for files that can be loaded by Clojure and ClojureScript (and
other Clojure platforms).

There will often be some parts of the code that vary between platforms. The
primary mechanism for dealing with platform-specific code is to isolate
that code into a minimal set of namespaces and then provide
platform-specific versions (.clj/.class or .cljs) of those namespaces.

To support cases where is not feasible to isolate the varying parts of the
code, or where the code is mostly portable with only small
platform-specific parts, 1.7 provides Reader Conditionals (
http://clojure.org/reader#The%20Reader--Reader%20Conditionals).

Reader conditionals are a new reader form that is only allowed in portable
cljc files. A reader conditional expression is similar to a cond in that it
specifies alternating platform identifiers and expressions. Each platform
is checked in turn until a match is found and the expression is read. All
expressions not selected are read but skipped. A final :default fallthrough
can be provided. If no expressions are matched, the reader conditional will
read nothing. The reader conditional splicing form takes a sequential
expression and splices the result into the surrounding code.

## Contributors

Thanks to all of those who contributed patches to Clojure 1.7:

Timothy Baldridge
Bozhidar Batsov
Brandon Bloom
Michael Blume
Ambrose Bonnaire-Sergeant
Aaron Cohen
Pepijn de Vos
Andy Fingerhut
Gary Fredricks
Daniel Solano Gómez
Stuart Halloway
Immo Heikkinen
Andrei Kleschinsky
Howard Lewis Ship
Alex Miller
Steve Miner
Nicola Mometto
Tomasz Nurkiewicz
Ghadi Shayban
Paul Stadig
Zach Tellman
Luke VanderHart
Jozef Wagner
Devin Walters
Jason Wolfe
Steven Yi

Also, continued thanks to the total list of contributors from all releases:
http://clojure.org/contributing#patches


Thanks!
Alex Miller

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
ClojureScript group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at http://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure/west 2016 in Seattle!

[Alex Miller]

Clojure/west 2016 will be held Apr 15-16 in Seattle at the Seattle Marriott
Waterfront.
You can find more info here: http://clojurewest.org

The CFP is open now and we encourage everyone to submit talks about
Clojure, ClojureScript, or other Clojure-related topics. You can find more
information about the process at: http://clojurewest.org/cfp

In particular we want to emphasize that we seek a diversity of voices at
the conference and we are happy to receive submissions and work with new as
well as experienced speakers. We are happy to review abstracts prior to
submission and suggest improvements. We can also connect speakers with
mentors or provide other assistance. Send any questions to
eve...@cognitect.com.

As a potential attendee, you can also add requested talk suggestions to the
list at:
https://github.com/clojurewest/clojurewest2016/wiki/Suggested-Topics

This is a new experiment to let the community suggest topics for talks
they'd like to see and for speakers to have a place to go for ideas.

Sponsorship opportunities are also available - this is a great way to reach
400-500 Clojure developers for hiring or other outreach. You can find more
information about sponsoring at http://clojurewest.org/sponsorship or
contact eve...@cognitect.com.

Hope to see you all there!
Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: clojure.spec

[Alex Miller]

There is a tutorial about spec in general at http://clojure.org/guides/spec

On Saturday, May 28, 2016 at 8:39:27 PM UTC-5, Jiyin Yiyong wrote:
>
>
>
> Looking forward to tutorials~

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: Clojure Google Summer of Code 2016 - Submit your project ideas!

[Alex Miller]

Nope.

On Monday, February 29, 2016 at 4:13:43 PM UTC-6, Colin Fleming wrote:
>
> That's a shame. Was any feedback given?
>
> On 1 March 2016 at 10:05, Alex Miller <a...@puredanger.com> wrote:
>
>> Unfortunately, we were informed today that Clojure was not selected as a 
>> 2016 Google Summer of Code organization.  :(
>>
>>
>>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Clojure Google Summer of Code 2016 - Submit your project ideas!

[Alex Miller]

Unfortunately, we were informed today that Clojure was not selected as a 
2016 Google Summer of Code organization.  :(


On Thursday, February 18, 2016 at 3:47:59 PM UTC-6, David Nolen wrote:
>
> Hello,
>
> We're approaching the end of the application period for organisation
> participation in Google Summer of Code 2016. This is a fantastic
> program that helps grow open source communities and gives students
> from around the world the opportunity to get paid to work on open
> source over the course of the summer. Clojure has participated four
> years in a row now, and many notable projects have benefitted as a
> result, including Clojure-in-Clojure, ClojureScript, Typed
> Clojure(Script), Clojure/Android, Incanter, and more.
>
> We would love to see Clojure participate again this year. In order to
> do so, we need to prepare our application which is due tomorrow. For
> our application to be a success, we need widespread involvement from
> the community to prepare a strong project ideas page. You can also
> review the ideas from the past several years to help you come up with
> new ideas.
>
> Please add your project ideas to the page at
> http://dev.clojure.org/display/community/Project+Ideas+2016. At this
> point, you are not committing to anything we just need your ideas.
> If you don't have edit rights to the wiki and don't want to sign up
> for an account, just post to the mailing list using [GSoC Idea] in the
> subject line, and one of the administrators will add it for you.
>
> Daniel Solano Gomez, Alex Miller, and Ambrose Bonnaire-Sergeant helped
> enormously last year, and I will be returning to help this year
> as an administrator.
>
> A big thanks to everyone who has participated in previous years as
> administrators, mentors, and students. We hope that this will be
> another successful Google Summer of Code for Clojure.
>
> Sincerely,
> David
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] clojurescript.org

[Alex Miller]

We are pleased to announce that http://clojurescript.org is now a site rather 
than a redirect to the github repo. Content was seeded from the CLJS wiki.

The site contribution process is the same as http://clojure.org - Contributor 
Agreement is required, but then contributions can be sent via PR. More info 
here:

http://blog.cognitect.com/blog/2016/8/15/welcome-clojurescript-org

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: [ANN] 2016 State of Clojure Community Survey

[Alex Miller]

Sorry for the delay on this but should be out this week!

On Sun, Feb 5, 2017 at 11:07 AM, Rangel Spasov <raspa...@gmail.com> wrote:

> Looking forward to the results! :)
>
> On Monday, December 12, 2016 at 6:43:58 AM UTC-8, Alex Miller wrote:
> > It's time for the annual State of Clojure Community survey!
> >
> > If you are a user of Clojure, ClojureScript, or ClojureCLR, we are
> greatly interested in your responses to the following survey:
> >
> > https://www.surveymonkey.com/r/clojure2016
> >
> > The survey contains four pages:
> >
> > 1. General questions applicable to any user of Clojure, ClojureScript,
> or ClojureCLR
> > 2. Questions specific to the JVM Clojure (skip if not applicable)
> > 3. Questions specific to ClojureScript (skip if not applicable)
> > 4. Final comments
> >
> > The survey will close December 23rd. We will release all of the data and
> our analysis in January. We are greatly appreciative of your input!
> >
> > If you have any questions, please let me know.
> >
> > Alex Miller
>
> --
> Note that posts from new members are moderated - please be patient with
> your first post.
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "ClojureScript" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojurescript/M-kV_AkcWJU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojurescript+unsubscr...@googlegroups.com.
> To post to this group, send email to clojurescript@googlegroups.com.
> Visit this group at https://groups.google.com/group/clojurescript.
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: No :exclude option for :require in Clojurescript?

[Alex Miller]

On Monday, September 26, 2016 at 1:24:27 PM UTC-5, mars0i wrote:
> On Monday, September 26, 2016 at 10:13:58 AM UTC-5, Alex Miller wrote:
> > I think this would do what you want:
> > 
> > (ns free.matrix-arithmetic
> >   (:require [clojure.core.matrix :as mx])
> >   (:refer clojure.core.matrix :exclude [e*]))
> 
> Thanks very much.  I didn't understand that the :refer expression is separate 
> from the :require expression in an ns statement.
> 
> This still produces an error in Clojurescript 1.9.229.  It seems to say that 
> :refer is not allowed in ns:
> 
> clojure.lang.ExceptionInfo: Only :refer-clojure, :require, :require-macros, 
> :use, :use-macros, and :import libspecs supported at line 1 ... :tag 
> :cljs/analysis-error

This may be one area where Clojure and ClojureScript differ (I don't follow 
ClojureScript with close enough attention to know). It's also possible that the 
spec is wrong and it should *not* include refer at all. In that case, I run the 
risk that my suggestion above that will be deemed invalid in a later alpha. :)  
You can also do the refer outside the ns as another (perhaps preferred) 
alternative:

(refer 'clojure.core.matrix :exclude '[e*])

> I just noticed some things about ns docstrings:
> 
> The docstrings for ns in Clojure 1.8.0 and 1.9.0-alpha12 don't mention :refer 
> at all.

Yeah, there are a number of places where the docstrings are imprecise. We are 
trying to bring more precision by defining specs here. The specs should help 
achieve greater alignment over time. 

> The docstring in Clojurescript 1.9.299 says that ":require supports :as, 
> :refer, and :rename", which I would read as implying that :refer belongs 
> somewhere inside a :require expression.  However, :exclude is only mentioned 
> in relation to :refer-clojure.

:require has support for some (but not all) refer functionality. :refer-clojure 
is just refer applied specifically to clojure.core so they share the same 
options pretty much.

Does this all make perfect sense? Perhaps not. Unfortunately ns and friends 
were added early in Clojure with perhaps less scrutiny than was prudent given 
their importance and they have evolved in non-optimal ways.

> At this point, :exclude is just something to be curious about for me, since I 
> rarely pull all or almost all of a namespace into another one.  Maybe I'll 
> leave it alone now that I've flagged some questions?  I don't understand 
> enough to submit relevant tickets.

I don't know that anything needs to be followed. If anything, I think a CLJ 
ticket about whether :refer should be supported in the ns spec is my biggest 
question.


-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: No :exclude option for :require in Clojurescript?

[Alex Miller]

I think this would do what you want:

(ns free.matrix-arithmetic
  (:require [clojure.core.matrix :as mx])
  (:refer clojure.core.matrix :exclude [e*]))


On Mon, Sep 26, 2016 at 9:54 AM, mars0i  wrote:

> > :exclude is not a valid option here (it's not having any effect). (doc
> require) mentions only :as and :refer as valid options in the libspec.
> :exclude is an option for :refer and :refer-clojure, not for :require.
> >
> > It's maybe interesting that the spec for ns does not report this problem
> here in :clojure.core.specs/prefix-list because of the use of keys*,
> which takes an open map view of options. I'll have to check with Rich if
> this is something we want to lock down more.
>
> I see.  Thanks.  If I wanted to pull in everything but e*, for example, I
> could use :exclude, but there's no reason to exclude anything if I'm only
> using specific, namespace-qualified functions from clojure.core.matrix.
>
> I had noticed that the docstring for require didn't mention exclude, but
> with some of the more complex macros and functions like require, there are
> sometimes minor points missing from docstrings.  (That's not a complaint.)
>
> I don't need :exclude at present, but I still can't figure out how I could
> pull in all functions but one from a namespace.  For example, the
> Clojurescript compiler doesn't like this:
>
> (ns free.matrix-arithmetic
>   (:require [clojure.core.matrix :as mx :refer :all :exclude [e*]]))
>
> The spec failure report:
>
> clojure.lang.ExceptionInfo: Only :as, :refer and :rename options supported
> in :require / :require-macros; offending spec: [clojure.core.matrix :refer
> :all :exclude [e*]] ...
>
> Similarly, this
>
> (ns free.matrix-arithmetic
>   (:use [clojure.core.matrix :exclude [e*]]))
>
> results in this
>
> clojure.lang.ExceptionInfo: Only [lib.ns :only (names)] and optionally
> `:rename {from to}` specs supported in :use / :use-macros; offending spec:
> [clojure.core.matrix :exclude [e*]] ...
>
> --
> Note that posts from new members are moderated - please be patient with
> your first post.
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "ClojureScript" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojurescript/y1vVdKp5EYw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojurescript+unsubscr...@googlegroups.com.
> To post to this group, send email to clojurescript@googlegroups.com.
> Visit this group at https://groups.google.com/group/clojurescript.
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: No :exclude option for :require in Clojurescript?

[Alex Miller]

On Sunday, September 25, 2016 at 10:41:33 PM UTC-5, mars0i wrote:
> This compiles in Clojure 1.9.0-alpha12 but not in Clojurescript 1.9.229:
> 
> (ns free.matrix-arithmetic
>   (:require [clojure.core.matrix :as mx :exclude [e*]]))
> 
> The error in Clojurescript is:
> 
> clojure.lang.ExceptionInfo: Only :as, :refer and :rename options supported in 
> :require / :require-macros; offending spec: [clojure.core.matrix :as mx 
> :exclude [e*]] ...
> 
> 
> 
> The code compiels in Clojurescript if I remove ":exclude [e*]".
> 
> Is :exclude going away as an option to require and :require, and 
> Clojurescript is ahead of Clojure?  Is this a bug?

:exclude is not a valid option here (it's not having any effect). (doc require) 
mentions only :as and :refer as valid options in the libspec. :exclude is an 
option for :refer and :refer-clojure, not for :require.

It's maybe interesting that the spec for ns does not report this problem here 
in :clojure.core.specs/prefix-list because of the use of keys*, which takes an 
open map view of options. I'll have to check with Rich if this is something we 
want to lock down more.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] Re: No :exclude option for :require in Clojurescript?

[Alex Miller]

On Mon, Sep 26, 2016 at 5:38 PM, António Monteiro 
wrote:

>
>
> FWIW, beware that locking this down further would have to account for
> ClojureScript's `:refer-macros` and `:include-macros`, etc.
>

CLJS will already need a different spec than CLJ for ns to account for this
so we're already planning on that.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Clojure infrastructure update

[Alex Miller]

I have been working with our hosting provider (thanks Contegix!) to upgrade
the hosts underneath *dev.clojure.org * (JIRA and
confluence) and *build.clojure.org * (Hudson).
The new hosts are much more recent versions of the OS and seem to be faster.

I cut *dev* over tonight. There were about 7 ticket changes in CLJS that
were lost due to when we copied the data today but I have manually
recreated those on the new version. afaik, everything is done with this
migration other than re-enabling notification emails on the new box which
will happen next. If you experience anything strange, please let me know.
Ideally, everything should look and work exactly the same.

*build* will take a bit longer before I make the switch. We upgraded from
the ancient version of Hudson we were on (which was blocking the ability to
do contrib builds with cljc) to newest version of Jenkins. Significant
portions of the build system are working again (kudos to Jenkins
community), but I still have some issues to work through and things to
test. Hopefully that will be next week.

I would dearly love to upgrade the JIRA/Confluence/Crowd versions we're on
too, but this is a significant undertaking intertwined with software
licensing and hosting considerations. Over the course of the last year, I
have spent several full weeks worth of time analyzing aspects of this and
doing (largely failing) test runs. It will get done eventually, but it's
not ready yet.

Alex

PS. By sending this I risk opening up questions about infrastructure and
other choices, so let me preempt some of those. :) We have no plans at this
time to: use anything other than jira or confluence, accept github PRs,
change the CA, change the license, or change the contribution model. These
topics have been rehashed on the mailing list a number of times and I don't
think anything has changed such that it's worth doing so again. If you want
to bend my ear, I will be at the Conj. :)

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] 2016 State of Clojure Community Survey

[Alex Miller]

It's time for the annual State of Clojure Community survey!

If you are a user of Clojure, ClojureScript, or ClojureCLR, we are greatly 
interested in your responses to the following survey:

https://www.surveymonkey.com/r/clojure2016

The survey contains four pages:

1. General questions applicable to any user of Clojure, ClojureScript, or 
ClojureCLR
2. Questions specific to the JVM Clojure (skip if not applicable)
3. Questions specific to ClojureScript (skip if not applicable)
4. Final comments

The survey will close December 23rd. We will release all of the data and our 
analysis in January. We are greatly appreciative of your input!

If you have any questions, please let me know.

Alex Miller

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure/west - Portland, OR - Mar 30-31, 2017

[Alex Miller]

Save the date for Clojure/west in Portland, OR!
March 30-31, 2017
Hilton Portland & Executive Towers
http://clojurewest.org

Registration: Clojure/west registration will open on Tuesday, January 17 at 4pm 
PST. A limited number of Early Bird tickets will be available for $350. After 
that Regular Registration tickets will be available for $400.

Call for Proposals: The Clojure/west Call for Proposals is now open 
(http://2017.clojurewest.org/cfp/)! Talks are 40 minutes in length in the 
following categories: Language, Experience Report, Library, Tools, Ideas and 
Fun.

Jan 11 - Call for Proposals Opens
Feb 3 - Call for Proposals Closes
Feb 10 - Speakers Notified

Submit a Topic: You can also submit topic ideas 
(https://github.com/clojurewest/clojurewest2017/wiki/Suggested-Topics) that 
others might be able to speak about. Anyone can feel free to draw from the list 
of ideas when writing their submissions.

Training: 
March 28-29, 9am-5pm: Intro to Clojure Training with Luke VanderHart ($400)
March 29, 9am-5pm: clojure.spec Workshop with Alex Miller ($300)

More details can be found on the Clojure/west website. Registration will open 
on Tuesday, January 17. 

Opportunity Grants: Apply for a Clojure/west Opportunity Grant! Details can be 
found on the website. Deadline to apply is Friday, February 3, 2017. 
http://2017.clojurewest.org/opportunity-grants/

Sponsorship: Interested in reaching an audience of 400+ Clojure developers? 
Learn more about sponsorship here!  http://2017.clojurewest.org/sponsorship/

Questions? Contact us at eve...@cognitect.com

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Bug (?) in clojure.spec (ClojureScript) with s/or inside s/and

[Alex Miller]

I just did a quick scan of this but I think this is the expected behavior. s/or 
conforms to a vector entry containing the tag of the path taken and the value.

s/and flows conformed values through each spec in the and, so order is 
important. All you're seeing is the conformed or flowing into the second spec 
in the and.

You might want to check the guide for more detail: 
http://clojure.org/guides/spec.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] Clojure infrastructure SSL

[Alex Miller]

The following bits of Clojure infrastructure are now https-only and
redirect all traffic from http to https:

https://build.clojure.org - Jenkins
https://dev.clojure.org/jira - JIRA
https://dev.clojure.org - Confluence

Let me know if you see anything amiss.

Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: How is Clojure loaded by java from cljs.jar?

[Alex Miller]

cljs.jar is self-contained (includes its dependencies) and includes Clojure 
itself (including clojure.main).

The cljs.jar is built using this script:

https://github.com/clojure/clojurescript/blob/master/script/build

You can walk through that process to learn more if needed.


On Saturday, August 5, 2017 at 12:15:31 PM UTC-5, Jay Martin wrote:
>
> In the "ClojureScript Compiler" section of the ClojureScript Quick Start 
> Guide , we run the build 
> script with the java command:
>
> java -cp cljs.jar:src clojure.main build.clj
>
>
> This command starts a JVM and loads the cljs.jar file and all of the 
> contents of the 'src' directory, to the JVM Classpath.
>
> According to the man page for the java program, clojure.main is a class 
> file, (I'm assuming this one 
> )
>  
> and build.clj is its argument.
>
> My question is: *How is the clojure.main class getting loaded to the 
> classpath?*
>
> Obviously clojure.main is part of Clojure. By unzipping the cljs.jar, I 
> see that it has a project.clj file with the following contents:
>
> (defproject org.clojure/clojurescript "0.0-SNAPSHOT"
>   :description "ClojureScript compiler and core runtime library"
>   :parent [org.clojure/pom.contrib "0.1.2"]
>   :url "https://github.com/clojure/clojurescript;
>   :license {:name "Eclipse Public License"
> :url "http://www.eclipse.org/legal/epl-v10.html"}
>   :jvm-opts ^:replace ["-Dclojure.compiler.direct-linking=true" "-Xmx512m" 
> "-server"]
>   :source-paths ["src/main/clojure" "src/main/cljs"]
>   :resource-paths ["src/main/cljs"]
>   :test-paths ["src/test/clojure" "src/test/cljs" "src/test/self" 
> "src/test/cljs_cp"]
>   :dependencies [[org.clojure/clojure "1.8.0"]
>  [org.clojure/data.json "0.2.6"]
>  [org.clojure/tools.reader "1.0.3"]
>  [org.clojure/test.check "0.10.0-alpha2" :scope "test"]
>  [com.cognitect/transit-clj "0.8.300"]
>  [org.clojure/google-closure-library 
> "0.0-20170519-fa0499ef"]
>  [com.google.javascript/closure-compiler-unshaded 
> "v20170626"]
>  [org.mozilla/rhino "1.7R5"]]
>   :profiles {:1.6 {:dependencies [[org.clojure/clojure "1.6.0"]]}
>  :uberjar {:aot :all :main clojure.main}}
>   :aliases {"test-all" ["with-profile" "test,1.5:test,1.6" "test"]
> "check-all" ["with-profile" "1.5:1.6" "check"]}
>   :min-lein-version "2.0.0")
>
>
> [org.clojure/clojure "1.8.0"] is listed as a dependency. Is this how 
> Clojure is getting loaded to the JVM Classpath?
>
> If so, how is this happening? It doesn't seem like the java program would 
> be smart enough to parse a project.clj file. 
>
>
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] [ANN] core.async 0.3.443

[Alex Miller]

core.async 0.3.443 is now available.

Try it via:  [org.clojure/core.async "0.3.443"]

0.3.443 includes the following changes:

   - ASYNC-159  - 
   promise-chan in ClojureScript is broken

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

Re: [ClojureScript] lein, clojurescript, and Java 9?

[Alex Miller]

This is a ClojureScript issue with Java 9 - same thing was mentioned 
yesterday here:

https://groups.google.com/d/msg/clojurescript/vcHhsLUCYlw/gW1ioB5PBAAJ



On Tuesday, December 5, 2017 at 6:22:00 PM UTC-6, Rob Nikander wrote:
>
>
>
> On Tuesday, December 5, 2017 at 7:03:32 PM UTC-5, Andy Fingerhut wrote:
>>
>> Try lein 2.8.1, if you are using any other version of Leiningen.  There 
>> are known issues with Leiningen versions less than that, combined with Java 
>> 9.
>>
>
> Looks like I'm running it already.
>
>   $ lein version
>   Leiningen 2.8.1 on Java 9.0.1 Java HotSpot(TM) 64-Bit Server VM 
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Inconsistency in creating keywords

[Alex Miller]

On Thursday, March 1, 2018 at 9:34:29 AM UTC-6, Thomas Heller wrote:
>
> Clojure follows the principle of "Garbage in, Garbage out" for a lot of 
> internal functions. 
>

I would say "unspecified input / unspecified output", however this is not 
one of those cases in my opinion. The keyword function creates keywords and 
they can be programatically used just fine. You can put them in a map, use 
them as accessors, etc. 
 

> Meaning you are responsible for ensuring that you only use valid data when 
> calling those functions as the validation itself carries overhead which the 
> core fns should not have.
>
> :a/0 fails because the reader does those checks and fails. The keyword fn 
> does no checks and lets you have your invalid keywords. They are still 
> invalid keywords though. Keywords are not allowed to start with numbers.
>

Really, that applies specifically to *literal* keywords (and actually even 
that is a matter of some lengthy debate and differences between clj and 
cljs). They are still valid keyword instances, just not ones that can be 
printed and read back by the reader.
 

> https://github.com/edn-format/edn might be a helpful reference about that 
> is allowed and what isn't.
>

Clojure(Script) code is not edn so the reader page is a better reference 
- https://clojure.org/reference/reader

These pages will not agree exactly - edn tends to be more restrictive in 
what it officially supports.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Inconsistency in creating keywords

[Alex Miller]

Regarding the keyword function, see the faq 
at https://clojure.org/guides/faq#unreadable_keywords

On Thursday, March 1, 2018 at 6:14:34 AM UTC-6, outr...@gmail.com wrote:
>
> I've encountered a problem when creating namespaced keywords using the 
> literal syntax, specifically using keywords which start with numbers. 
>
> If I try using the literal syntax, entering the following at the REPL, I 
> get the exception which follows it:
>
> :a/0
> ;= clojure.lang.ExceptionInfo: NO_SOURCE_FILE [line 1, col 5] Invalid 
> keyword: :a/0. {:type :reader-exception, :ex-kind :reader-error, :file 
> "NO_SOURCE_FILE", :line 1, :col 5} ...
>
> If instead I use the the keyword function, it produces the desired result:
>
> (keyword "a" "0")
> ;= :a/0
>
>
> It seems I can get away with almost anything using the keyword function. 
> For example:
>
> (keyword "a" "0/1")
> ;= :a/0/1
>
> I'm wondering then, what is the "correct" behaviour if there is such a 
> thing in this case? I know that in Clojure the behaviour appears once again 
> to be slightly different, and the main docs seem to cater more to Clojure 
> than to CLJS.
>
> Thank you,
> Ali
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Inconsistency in creating keywords

[Alex Miller]

There's actually a lot of history and several open tickets about this 
specific question of whether keywords can start with a digit. The original 
intent (and the reader reference page) is that it would match symbols in 
that leading digits are not allowed. However, there is a bug in the regex 
that lead to them being accepted.

We tried to fix this bug several years ago and it broke a lot of existing 
code that was relying on the ability to do this. We decided at that point 
that there was no reason to take this away. The lingering tickets are to 

a) fix the regex to do this on purpose rather than on accident (and this is 
also the reason why some of your examples work and some do not)
b) update the reference pages to explicitly include this
c) sync up edn rules with clojure rules

So, if you want to be really safe and "to the spec" right now, then I would 
say, don't use leading digits in keywords. Realistically though, we're 
never going to disallow those and eventually I expect them to be 
"officially" ok. 

For leading digits in namespaces, that may actually violate Java package 
rules, in which cases we would not be able to allow that.

On Friday, March 2, 2018 at 12:35:26 AM UTC-6, outr...@gmail.com wrote:
>
> Thank you both for the links, especially the FAQ page. As an aside I was 
> looking for something like the namespace function and am glad I found it.
>
> Something is still confusing me however. If we follow the reader docs 
> which Alex posted, "Symbols begin with a non-numeric character", and 
> "Keywords are *like* symbols" (emphasis mine, this may be open to 
> interpretation) hence also shouldn't begin with a non-numeric character. 
> But if you try the following in either Clojure or (Script)'s REPLs, they 
> work just fine:
>
> :0
> ;= :0
>
> Further, using the respective reader-string functions also yields:
> (read-string ":0")
> ;= :0
>
> So this would indicate that whatever is written in the docs is not 
> necessarily being enforced in the reader, is that correct?  
>

> It seems that as far as the reader is concerned, keywords can begin with a 
> numeric but the name portion (after the /) of a namespaced keyword can't. 
> In other words :0 is legal, :a/0 isn't. 
>
> Interestingly enough, 
> :0/a
> ;= :0/a
>
> is also legal within each language's reader.
>
> In which case, why are :0 and :0/a legal but not :a/0?
>
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Creating a map entry

[Alex Miller]

On Thursday, October 18, 2018 at 4:07:32 AM UTC-5, Khalid Jebbari wrote:
>
>
> PS: I couldn't get clojure cli to download criterium to run the benchmark, 
> so I ended up using the REPL provided by in my current app setup (based on 
> Clojure 1.9.0, Boot 2.8.2 and criterium 0.4.4, the latest stable versions). 
> Here's the command I ran and the error:
>
> ```
> > clj -Sdeps "{:deps {org.clojure/clojure {:mvn/version \"1.9.0\"} 
> criterum {:mvn/version \"0.4.4\"}}}"
> Error building classpath. Could not find artifact 
> criterum:criterum:jar:0.4.4 in central (https://repo1.maven.org/maven2/)
>

You misspelled "criterium" in your deps.

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: problem with cljs, local dependencies, and src path

[Alex Miller]

On Sunday, December 30, 2018 at 3:51:29 PM UTC-6, Rob Nikander wrote:
>
>
>
> On Sunday, December 30, 2018 at 3:27:21 PM UTC-6, Phill Wolf wrote:
>>
>> By the way, is there a deps.edn in the hello2 directory?
>>
>
> Yes, there is. I was just working on this again I think I figured it out. 
> Two things confused me. Maybe it's working as intended, but it seems these 
> could be bugs.
>
> 1. If I update a deps.edn file in the dependency (hello2) to change the 
> :paths there, the classpath is not updated in my project (hello1). I need 
> to run `rm -rf .cpcache` in my project's directory so that it picks up the 
> change. 
>

This is a known issue with local deps and I have a (somewhat complicated) 
plan to address it but it's down the stack a bit.

It's better to use -Sforce when you make a change like this than to rm the 
entire cpcache. force will force the classpath to be recomputed (but 
doesn't delete all of the other, potentially still valid, parts of the 
cache).
 

>
> 2. If I don't specify :paths in the dependency's (hello2) deps.edn file, 
> then it will use the :paths is in the main project (hello1). That seems odd 
> to me that the inheritance flows that way.  I imagined that by leaving 
> deps.edn black in hello2, hello2 was specifying it's src path to be the 
> default ("src").
>

This is another known issue which has to do with how the deps.edn files are 
read, which ties into a rework of how the "current directory" is 
interpreted throughout the resolution of local relative paths.
 

>
> Rob
>
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: Old "critical" bug in core.async?

[Alex Miller]

Can certainly be fixed, probably needs to be re-checked to see if it is 
still actually a bug. Would be happy to have a patch.

On Saturday, January 26, 2019 at 8:03:56 AM UTC-6, Rob Nikander wrote:
>
> I was trying (again) to learn and use core.async. I noticed this and it 
> worried me:
>
> https://dev.clojure.org/jira/browse/ASYNC-73
>
> A bug marked "critical" that's unfixed for 4.5 years? Does it mean that 
> certain things in core.async cannot be fixed?
>
> Rob
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To post to this group, send email to clojurescript@googlegroups.com.
Visit this group at https://groups.google.com/group/clojurescript.

[ClojureScript] Re: cljs.jar not pointing to the most updated version on https://clojurescript.org/guides/quick-start

[Alex Miller]

Updated, thanks.

Alex

On Thursday, July 25, 2019 at 3:28:23 AM UTC-5, Sigmund Tzeng wrote:
>
> Hello there,
>
> Currently the r1.10.516 is linked to which gave me InvalidPathException 
> when compiled with --optimizations advanced on my Win10 laptop.
>
> Solved with r1.10.520
>
> Hope this helps.
>
> Best regards,
>
> Sigmund Tzeng
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojurescript/d6aaf7d3-9c70-4087-9eed-b3658a6205e0%40googlegroups.com.

Re: [ClojureScript] lein gorilla :port 8990 fails because "Call to clojure.core/ns did not conform to spec"

[Alex Miller]

Well, it's not OP's file, the bad file is ring/util/mime_type.clj, which 
looks like it was fixed in 2014 
(https://github.com/ring-clojure/ring/commit/a05e026d85611cb179a1352d569d7c68713f792c#diff-ed2c15fc701c576b461d6967f0f81e91),
 
so must need to pull in a newer version somewhere.



On Monday, October 7, 2019 at 5:43:16 PM UTC-5, Mark Nutter wrote:
>
> The important bit is the part that says ":val ((require [clojure.string 
> :as str]))". I believe that is telling you that you have "(require 
> [clojure.string :as str])" inside your namespace declaration, but you need 
> ":require" (leading colon) instead of "require" when you're putting it 
> inside the "(ns ...)" declaration.
>
> On Mon, Oct 7, 2019 at 3:42 PM Kelvin T > 
> wrote:
>
>> This is my first time working with clojure, and I am struggling to run 
>> gorilla repl. Any help would be greatly appreciated.
>> Below is the stack trace:
>>
>> clojure.lang.Compiler$CompilerException: Syntax error macroexpanding 
>> clojure.core/ns at (ring/util/mime_type.clj:1:1).
>> #:clojure.error{:phase :macro-syntax-check, :line 1, :column 1, :source 
>> "ring/util/mime_type.clj", :symbol clojure.core/ns}
>>  at clojure.lang.Compiler.checkSpecs (Compiler.java:6971)
>> clojure.lang.Compiler.macroexpand1 (Compiler.java:6987)
>> clojure.lang.Compiler.macroexpand (Compiler.java:7074)
>> clojure.lang.Compiler.eval (Compiler.java:7160)
>> clojure.lang.Compiler.load (Compiler.java:7635)
>> clojure.lang.RT.loadResourceScript (RT.java:381)
>> clojure.lang.RT.loadResourceScript (RT.java:372)
>> clojure.lang.RT.load (RT.java:463)
>> clojure.lang.RT.load (RT.java:428)
>> clojure.core$load$fn__6824.invoke (core.clj:6126)
>> clojure.core$load.invokeStatic (core.clj:6125)
>> clojure.core$load.doInvoke (core.clj:6109)
>> clojure.lang.RestFn.invoke (RestFn.java:408)
>> clojure.core$load_one.invokeStatic (core.clj:5908)
>> clojure.core$load_one.invoke (core.clj:5903)
>> clojure.core$load_lib$fn__6765.invoke (core.clj:5948)
>> clojure.core$load_lib.invokeStatic (core.clj:5947)
>> clojure.core$load_lib.doInvoke (core.clj:5928)
>> clojure.lang.RestFn.applyTo (RestFn.java:142)
>> clojure.core$apply.invokeStatic (core.clj:667)
>> clojure.core$load_libs.invokeStatic (core.clj:5985)
>> clojure.core$load_libs.doInvoke (core.clj:5969)
>> clojure.lang.RestFn.applyTo (RestFn.java:137)
>> clojure.core$apply.invokeStatic (core.clj:669)
>> clojure.core$use.invokeStatic (core.clj:6093)
>> clojure.core$use.doInvoke (core.clj:6093)
>> clojure.lang.RestFn.invoke (RestFn.java:421)
>> 
>> ring.middleware.content_type$eval2277$loading__6706__auto2278.invoke 
>> (content_type.clj:1)
>> ring.middleware.content_type$eval2277.invokeStatic 
>> (content_type.clj:1)
>> ring.middleware.content_type$eval2277.invoke (content_type.clj:1)
>> clojure.lang.Compiler.eval (Compiler.java:7176)
>> clojure.lang.Compiler.eval (Compiler.java:7165)
>> clojure.lang.Compiler.load (Compiler.java:7635)
>> clojure.lang.RT.loadResourceScript (RT.java:381)
>> clojure.lang.RT.loadResourceScript (RT.java:372)
>> clojure.lang.RT.load (RT.java:463)
>> clojure.lang.RT.load (RT.java:428)
>> clojure.core$load$fn__6824.invoke (core.clj:6126)
>> clojure.core$load.invokeStatic (core.clj:6125)
>> clojure.core$load.doInvoke (core.clj:6109)
>> clojure.lang.RestFn.invoke (RestFn.java:408)
>> clojure.core$load_one.invokeStatic (core.clj:5908)
>> clojure.core$load_one.invoke (core.clj:5903)
>> clojure.core$load_lib$fn__6765.invoke (core.clj:5948)
>> clojure.core$load_lib.invokeStatic (core.clj:5947)
>> clojure.core$load_lib.doInvoke (core.clj:5928)
>> clojure.lang.RestFn.applyTo (RestFn.java:142)
>> clojure.core$apply.invokeStatic (core.clj:667)
>> clojure.core$load_libs.invokeStatic (core.clj:5985)
>> clojure.core$load_libs.doInvoke (core.clj:5969)
>> clojure.lang.RestFn.applyTo (RestFn.java:137)
>> clojure.core$apply.invokeStatic (core.clj:669)
>> clojure.core$use.invokeStatic (core.clj:6093)
>> clojure.core$use.doInvoke (core.clj:6093)
>> clojure.lang.RestFn.invoke (RestFn.java:512)
>> compojure.route$eval2269$loading__6706__auto2270.invoke 
>> (route.clj:1)
>> compojure.route$eval2269.invokeStatic (route.clj:1)
>> compojure.route$eval2269.invoke (route.clj:1)
>> clojure.lang.Compiler.eval (Compiler.java:7176)
>> clojure.lang.Compiler.eval (Compiler.java:7165)
>> clojure.lang.Compiler.load (Compiler.java:7635)
>> clojure.lang.RT.loadResourceScript (RT.java:381)
>> clojure.lang.RT.loadResourceScript (RT.java:372)
>> clojure.lang.RT.load (RT.java:463)
>> clojure.lang.RT.load (RT.java:428)
>> clojure.core$load$fn__6824.invoke (core.clj:6126)
>> clojure.core$load.invokeStatic (core.clj:6125)
>> clojure.core$load.doInvoke (core.clj:6109)
>> clojure.lang.RestFn.invoke 

[ClojureScript] Re: Let's make ClojureScript more approachable for beginners

['Alex Miller' via ClojureScript]

I actually spent some time looking at this last month for whether to 
include in Clojure 1.10.2. While the patch does "work", I am somewhat 
undecided still about whether it's the best approach so I decided to wait 
until 1.11 to consider it more, but it is high on the list. Feel free to 
vote at 
https://ask.clojure.org/index.php/751/clojure-java-shell-sh-hangs-calling-xdg-open.

BTW, it's high on my list because it has votes on https://ask.clojure.org - 
please make your priorities known there, we're looking at vote counts!  

Alex

On Sunday, October 11, 2020 at 10:37:40 AM UTC-5 hexagonr...@gmail.com 
wrote:

> > The REPL hangs on Linux
>
> The patch for this bug have been available for over a year (
> https://clojure.atlassian.net/browse/CLJ-2493). I hope the maintainers 
> eventually get around to merging it.
>

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojurescript/0bdf-1c0e-496b-93f7-f918f2fe83c4n%40googlegroups.com.

[ClojureScript] State of Clojure 2021 survey

['Alex Miller' via ClojureScript]

Hello all,

It's that time of year again! Please complete the State of Clojure 2021 
survey, an important tool for tracking our community over the last decade.

https://www.surveymonkey.com/r/clojure2021

Thanks!

Alex

-- 
Note that posts from new members are moderated - please be patient with your 
first post.
--- 
You received this message because you are subscribed to the Google Groups 
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojurescript+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojurescript/02e91b66-9d63-4523-ae08-db3718255d4bn%40googlegroups.com.