On Sat, Dec 9, 2017 at 11:37 PM, Alan Thompson wrote:
> Hi - Just downloaded the new Clojure 1.9.0 package. When I tried the repl
> I noticed that it doesn't respond to either `exit` or `quit` as one might
> expect from the lein repl:
>
> ~/cool/tools > clj
> Clojure 1.9.0
> user=> (+ 2 3)
> 5
>
I think it's a great idea and it may even be a missing piece in the 'Grow,
not Break' approach https://youtu.be/oyLBGkS5ICk?t=1946 , namely to the
problem that good names are hard to come by.
Suppose a library author wants to make a breaking change to some function.
They change the doc-name of
Hi, all
I’m happy to announce the first release of Pinpointer, yet another
implementation of spec error reporter based on a precise error analysis.
- https://github.com/athos/Pinpointer
Pinpointer provides functionalities very similar to the existing spec error
reporters (eg. Expound[1], Inspe
I've just released a wrapper
around https://github.com/jvm-profiling-tools/async-profiler that allows
controlling the profiler directly from the REPL of the program you want to
profile. The JAR file ships the profiling agent and the flamegraph
generation script from https://github.com/brendangr
Totally awesome - nice work!
--
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 th
I apologize, I'm not certain of the right name for this.
I'm pulling in libgdx and its dependencies. In Leiningen, my dependencies
vector looks like this:
:dependencies [[org.clojure/clojure "1.8.0"]
[com.badlogicgames.gdx/gdx "1.9.6"]
[com.badlogicgames.gdx/
On 11/12/17 20:47, Jonathan Fischer wrote:
> com.badlogicgames.gdx/gdx {:mvn/versin "1.9.6"}
Typo?
--
David
--
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 memb
Ha, I think that must’ve snuck in there during editing. Fixing that particular
typo didn’t help any. :D
> On Dec 11, 2017, at 12:22 PM, David Bürgin wrote:
>
> On 11/12/17 20:47, Jonathan Fischer wrote:
>> com.badlogicgames.gdx/gdx {:mvn/versin "1.9.6"}
>
> Typo?
>
>
> --
> David
>
> --
>
Hm, looks like this is an open issue:
https://dev.clojure.org/jira/browse/TDEPS-12
--
David
--
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
Yep, that looks like what I'm seeing. Thanks!
--
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 un
Hi there,
I have been trying to shake this thought for a while now. Essentially, my
thought was if you can return a function why not decision component of an
IF, WHEN or SOME statement? That would give you a re-usable named choice.
Then you could write:
(celebration: do-something do-something-
I talked a bit about this in my video on Boolean Blindness:
https://www.youtube.com/watch?v=K1LaaJMscCc
Might be worth a watch.
On Mon, Dec 11, 2017 at 4:56 PM, Stephen Feyrer
wrote:
> Hi there,
>
> I have been trying to shake this thought for a while now. Essentially, my
> thought was if you
Hi Didier,
Are you familiar with Unison (http://unisonweb.org/)? It has this same
feature. Functions are named by a hash of their code (the AST). Names refer
to hashes. So if you want to recompile a function, you can optionally
choose newer versions of all of the functions. But changing a funct
Very cool! Excellent work.
On Monday, December 11, 2017 at 7:23:38 AM UTC-7, OHTA Shogo wrote:
>
> Hi, all
>
> I’m happy to announce the first release of Pinpointer, yet another
> implementation of spec error reporter based on a precise error analysis.
>
> - https://github.com/athos/Pinpointer
I'll have a look at all these other projects, its very interesting. Unison
seems to embody the spirit or Richs talk about never changing anything too.
I guess I was trying to think how could you bring some of this to Clojure.
And in a way, if the constructs like functions had an id and a name, y
This might be a step towards a more clojury way:
http://blog.datomic.com/2012/10/codeq.html
John
On Mon, Dec 11, 2017 at 7:53 PM, Didier wrote:
> I'll have a look at all these other projects, its very interesting. Unison
> seems to embody the spirit or Richs talk about never changing anything t
s/def docs says: "Given a namespace-qualified keyword or resolvable symbol
..."
But I'm unable to s/def a spec using a resolvable symbol:
(def foo 123)
(s/def foo int?)
(s/get-spec foo) => nil
(s/get-spec 'foo) => nil
(s/get-spec #'foo) => #object[clojure.spec.alpha$spec_impl$reify__797
0x7215d
On Monday, December 11, 2017 at 7:01:20 PM UTC-6, Didier wrote:
>
> s/def docs says: "Given a namespace-qualified keyword or resolvable symbol
> ..."
>
Symbols are used to register function specs (with the same qualified symbol
as the var it's stored with).
> But I'm unable to s/def a spec u
What if the code segments were hashed by zipper coordinates instead of
line-column location? I like this idea of structurally navigating the code
as an AST of EDN :)
John
On Mon, Dec 11, 2017 at 7:55 PM, John Newman wrote:
> This might be a step towards a more clojury way: http://blog.datomic.c
FWIW, this was a bit like the approach taken in Expectations – functions were
given names based on a hash of the code in the test, meaning that old functions
(tests) stayed around if you change the tests (which created a newly named
function). This led to problems with REPL usage since you could
> On Dec 11, 2017, at 6:42 AM, Alexander Yakushev wrote:
>
> I've just released a wrapper around
> https://github.com/jvm-profiling-tools/async-profiler that allows controlling
> the profiler directly from the REPL of the program you want to profile. The
> JAR file ships the profiling agent a
Alex and Luke, thank you for your kind words!
Regarding your questions, Luke. #3. Authors of async-profiler promise that
it's quite low-overhead. Of course, some experimentation and benchmarking
is needed, but I think it is possible to have the profiler always on. Some
work would be required to
Hi Tim,
Thank you.
--
Kind regards
Stephen.
On 11 December 2017 at 23:58, Timothy Baldridge
wrote:
> I talked a bit about this in my video on Boolean Blindness: https://www.
> youtube.com/watch?v=K1LaaJMscCc
>
> Might be worth a watch.
>
> On Mon, Dec 11, 2017 at 4:56 PM, Stephen Feyrer
> w
23 matches
Mail list logo
