Re: Q: How to find out how much Clojure you use

2017-10-26 Thread Didier 
I think the Grimoire heatmap is over itself maybe?

core/for being top defs, beating core.map does not match up with crossclj 
usage of the two.

On Wednesday, 25 October 2017 23:05:12 UTC-7, Gary Trakhman wrote:
>
> Grimoire has a usage heatmap, I think it just might be over a few 
> projects: https://www.conj.io/heatmap
>
> On Oct 26, 2017 7:40 AM, "Erik Assum" > 
> wrote:
>
>> Eric Normand did some research on this some time ago:
>>
>> http://www.lispcast.com/100-most-used-clojure-expressions
>>
>> Erik. 
>> -- 
>> i farta
>>
>> 25. okt. 2017 kl. 23:05 skrev Colin Fleming > >:
>>
>> IntelliJ has a nice Productivity Guide feature which works sort of like 
>> this - every time you use a certain feature it's recorded, and you can see 
>> a table of the various features, how often you used it and when you last 
>> used it. You can click on each feature to see documentation about how it 
>> works. It's really handy - I haven't done this for a while, but I used to 
>> browse all the "Never used" features, find one that looked interesting and 
>> try it out. Something similar for Clojure could be really nice.
>>
>> On 26 October 2017 at 09:32, Robert Levy 
>> > wrote:
>>
>>> That would be very interesting, especially at an aggregate level, to 
>>> visualize clusters of Clojure sub-idioms (?) based on code people have 
>>> publicly shared with their name attached.  One way to get going with that 
>>> quickly would be write some Clojure code to collect, index, and analyze the 
>>> data in Elasticsearch so that you could use the various readymade 
>>> visualization tools that come with Kibana for "dashboards".  For one thing 
>>> you could look at geographical patterns, to see if that's even a thing. :)  
>>> And results over time, to see for example patterns of adoption.  Do people 
>>> still use refs and agents?  Does anyone really use transducers? ;) I am 
>>> curious to see the results if someone does this. It would be a good project 
>>> short enough for a Clojure meetup probably, given some preparation.
>>>
>>> On Tue, Oct 24, 2017 at 11:24 PM, Andy Marks >> > wrote:
>>>
 It seems like everytime I watch another Clojure/Conj video or finish 
 another 4Clojure problem, I learn about another piece of the Clojure core 
 set of functions that I was unfamiliar with... which prompted the question:

 *What subset of the Clojure core API do I use?  Which functions are my 
 favourites?  Which have I never used?*

 Ideally, I would like to point a tool at my GitHub account, have it 
 look through all the Clojure code I've written and give me a histogram of 
 my usage of the clojure.core API.

 My question to you all is: does anyone know of a tool that provides 
 some of this functionality?
  

 -- 
 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 
 
 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 
 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 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> -- 
>>> 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 
>>> 
>>> 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 
>>> 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 .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> 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 
>> 
>> 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 
>> 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 .
>> For m

We present: DevTools for re-frame!

2017-10-26 Thread Saskia Lindner 
Hi everyone!

This summer, we worked on a devtool for re-frame, called re-frame trace. 
Daniel Compton who had initially started the project supported us 
throughout the course of the summer along with a bunch of people from the 
Clojure community. Thanks so much to all of you!

Our intention was to improve the developer experience by presenting the 
application data in a clear and browsable way. Information about events, 
subscriptions and renderings are being displayed while interacting with the 
application and it is possible to inspect the current app-state. 


Go try it out: https://github.com/Day8/re-frame-trace

If you want to get an impression of how it works, Matt Huebert has set up a 
sample application showing the tool in use: 
https://mhuebert.github.io/shadow-re-frame/ (forked version of re-frame 
trace)

And if you're interested in more information, read our blog post here: 
http://www.daiyi.co/dev-diary/


We would love to get your feedback. Find us as daiyi and saskia on 
Clojurians Slack (https://clojurians.slack.com/) via direct message or in 
the #re-frame channel. 


Cheers, 

Chris & Saskia

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Bitcoind API for Clojure/Java (experimental).

2017-10-26 Thread eliassonaand via Clojure 
 

I'm interested in Bitcoin and cryptocurrencies.

So I installed bitcoind on my laptop and started playing with the CLI. 

I also tried some Java and Clojure libs that builds on top of the CLI.


After a while I decided to write my own library for it.  

Specifically I wanted to see if it was possible to parse information from 
the CLI, (which is mostly in JSON format)

and generate the API for Clojure and Java by using AOT, Instaparse, macros 
etc.

Don't really know if it's usable for anyone but it was a fun exercise.


The result can be found here: https://github.com/eliassona/bitcoinrpc



Anders



-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Clojure 1.9.0-beta3

2017-10-26 Thread Leon Grapenthin 
Have you considered calling it clojure.spec.alpha.skip-macros
?

Would make sense if you intend to ignore that setting in 2.0 (or any later 
release with spec nonalpha)

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Clojure 1.9.0-beta3

2017-10-26 Thread Alex Miller 
The system properties are intended to have the same meaning before and
after alpha status so don't have alpha in their name (same applies to other
spec system properties).

On Thu, Oct 26, 2017 at 2:50 PM, Leon Grapenthin 
wrote:

> Have you considered calling it clojure.spec.alpha.skip-macros
> ?
>
> Would make sense if you intend to ignore that setting in 2.0 (or any later
> release with spec nonalpha)
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Clojure" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/clojure/jKsa9asMFm4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> clojure+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

In cljs a/go expands into clojure.core.async/go instead of cljs.core.async.macros/go

2017-10-26 Thread Vitalie Spinu 
Hi,

I am having hard time writing a macro in cljc which uses core.async/go 
macro. 

Minimal project that illustrates the problem is here 
.  In a 
nutshell:

core.clj:

(ns cljproj.core
  (:require
   #?(:clj  [clojure.core.async :refer [go >! !  (macroexpand-1 '(tt (a/chan)))
(clojure.core.async/go (clojure.core/println (clojure.core.async/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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Expectations 2.2.0-rc3

2017-10-26 Thread Sean Corfield 
Expectations – an expressive unit testing framework

https://github.com/clojure-expectations/expectations/releases/tag/v2.2.0-rc3
https://github.com/clojure-expectations/expectations/blob/master/CHANGELOG.md

The main focus of the 2.2.0 release is adding compatibility with clojure.test 
tooling by introducing named tests. Release Candidate 3 restores almost all of 
Expectations’ original clarity of failure messages (shoehorning them into 
clojure.test’s reporting structure), as well as leveraging clojure.test in a 
way that is now compatible with Cursive (thank you to Colin for his patience on 
Slack while I worked through those issues over the last few days).

If you’re using Expectations 2.1.x or earlier and wonder why clojure.test 
compatibility is worthwhile, please read:

https://clojure-expectations.github.io/clojure-test.html#migrating-to-clojure-test

If you’ve been using earlier 2.2.0 releases, be aware of a potentially breaking 
change in RC 3: expectations.clojure.test now defines its own expect macro – 
the symbol expect is no longer handled “magically” by defexpect (this improves 
line number reporting, amongst other things) – and all public symbols from 
expectations are now available in expectations.clojure.test so you should 
switch to using only the latter namespace, not both! (and, yeah, this is going 
to break the World Singles test suite when I update our code to use RC 3 so I 
will share your pain!)

Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN
An Architect's View -- http://corfield.org/

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.