That looks very helpful, thanks. I've been bitten by this hard in the past
- I wanted to play with a few different Processing jars in Quil, none of
which had Maven versions; and even using lein-localrepo, it was excessively
complex to add these jars to my local maven repo just so I could play with
Hi Steven,
A few thoughts:
1. You may want to look at
https://github.com/clojure/test.generative/blob/master/data-model.org.
2. I don't think you want a ref for *assertion-results* -- I am not aware
of any use cases that would need transactions. In any case the choice of
reference type probably
Here is a similar algorithm I did for work a while back:
(defn- find-next-node [deps used-nodes]
(some (fn [[k v]] (if (empty? (remove used-nodes v)) k)) deps))
(defn topsort
"Takes a map of dependencies between items and performs a topological
sort.
E.g. (topsort {1 [2 3] 3 [] 2 [3]}) =
Also yours explodes if given a circular dependency. There is no way around
throwing an exception, but it is always nice not to have stack overflows in
your code:
(def graph
{"a" {:dependencies ["b" "d"]}
"b" {:dependencies ["c" "e"]}
"c" {:dependencies ["d" "e"]}
"d" {:dependencie
I'm happy to announce, that Incanter 1.5.0 was pushed to Clojars. Full list
of changes is in the Changelog:
https://github.com/liebke/incanter/blob/master/Changes.md, please check the
"Known issues" section.
Incanter (http://incanter.org/) is a Clojure-based, R-like platform for
statistical comput
Ben,
Thanks for the feedback... and I'm sorry it to so long to say thanks (I've
been traveling).
In terms of the lack of being hygienic, I discuss that in the next
paragraph in the blog post the OP took the macro from.
But I really appreciate your thoughts on error messages. As I develop
macros,
I recently upgraded clojure-refactoring to Clojure 1.5.0 and nREPL. See if
it helps you. https://github.com/luckykevin/clojure-refactoring
On Thursday, March 21, 2013 9:05:57 AM UTC+8, Dave Kincaid wrote:
>
> I'm wondering if there are any refactoring tools around for working with
> Clojure proj
Hi, I recently upgrade old clojure-refactoring repo to Clojure 1.5.0 and
nREPL. See if it help you. https://github.com/luckykevin/clojure-refactoring
On Thursday, March 21, 2013 9:05:57 AM UTC+8, Dave Kincaid wrote:
>
> I'm wondering if there are any refactoring tools around for working with
> C
Thanks for the new release.
Will the changes be also available in files which are downloadable on
this link (http://incanter.org/downloads/)?
I used these files often to create some ad hoc graphics or a method to
show others what can be done.
Am 09.06.2013 14:16, schrieb Alex Ott:
I'm happ
I'll try to upload new versions there during next days. Right now, the
simplest way to get new version is to create new lein project & add
incanter as dependency:
(defproject test-incanter "0.1.0-SNAPSHOT"
:description "FIXME: write description"
:url "http://example.com/FIXME";
:license {:na
I'd like to mention that expectations* has 0 open pull requests, 0 open
issues, and is very actively maintained**. Steven, I don't want to
discourage you from creating your own testing framework, I think everyone
should, it's a very educational experience.
I just wanted to be clear that no one
nrepl has macroexpansion, so you can already have 1/2 of what you want -
better than nothing.
On Friday, March 22, 2013 9:42:10 PM UTC-4, Alex Baranosky wrote:
>
> I'd really like to see a way to factor to code that uses ->/->> and back
> again.
>
> On Fri, Mar 22, 2013 at 12:01 PM, Laurent PETI
I've written the 2nd one in emacs lisp, the first one would be even easier.
If you're using emacs, you should give it a shot, it was a great learning
experience for me.
On Friday, March 22, 2013 10:54:36 PM UTC-4, Russell Mull wrote:
>
> I find myself doing that a lot by hand, a tool to help wou
Thanks for the feedback. I'l look into #1. Regarding #2, we just wanted a
side-effecty (mutable) way of adding assertion-results within a test. I
suppose I could use (trans []) and let users use conj! although the fact
that transient keeps saying "alpha, use at your own risk" concerns me a bit.
Jay (and others),
First of all, you must understand where test2 came from. It started as a
bunch of people** in #clojure discussing what we'd change about
clojure.test if we could.
We realized we can't change clojure.test because (1) this would break
backwards compatibility, and (2) clojure.test
There's a few things that I know the SPEC needs to address.
- Pending tests
- Some flexible concept of around-all and around-each that allow separating
Definers from Runners (currently, to implement clojure.test's
once-fixtures, it requires a custom Definer *and* a custom Runner)
- Whether Run
For using Incanter in my onw projects I use Leiningen, but the *.exe and
*.jar files are cool to show Incanter to persons which have no IDE for
clojure right at hand (or any other toll/libarary which can be used with
clojure), and it is a nice tool to make some demos.
Am 09.06.2013 18:18, sc
On Jun 9, 2013, at 1:07 PM, Steven Degutis wrote:
> I think we all agree that it's extremely important to discuss the SPEC as a
> community. In fact, since this is a pre-ANN, let's consider this thread the
> perfect place for such a discussion.
I suggest that surveying users of the various exi
On Sun, Jun 9, 2013 at 11:07 AM, Steven Degutis wrote:
> We realized we can't change clojure.test because (1) this would break
> backwards compatibility, and (2) clojure.test is really slow-moving since it
> lives inside Clojure.
Are there any JIRA tickets open against clojure.test? That would se
I agree, we should survey users of existing tools. The thing is, we *are*
those users. The aforementioned brainstorming session was just what you're
suggesting. That's what I'm suggesting this mailing list thread be.
For example, I never use Midje's "a => b" outside of a macro. I always wrap
fa
FWIW, about the only thing about clojure.test that I miss occasionally
when using Expectations is 'each' fixtures for a subset of tests but
the work involved in wrapping an expression in a try/finally with the
resource setup and tear down I need is usually so minimal that's it's
not even worth writ
> Are there any JIRA tickets open against clojure.test? That would seem
> to be a good place to start.
>
Good idea, that helps for gathering data about use-cases.
> If someone (with a signed CA on file) wants to step up and maintain
> clojure.test, even tho' it's part of core Clojure right
On Sun, Jun 9, 2013 at 5:50 PM, Steven Degutis wrote:
> Changing clojure.test seems like the wrong way to go. Being attached to a CA
> makes it hard to contribute to.
It's a one-off action. Sign it, send it in. Then you can contribute to
Clojure or any of its contrib libraries from then on. Not e
On Sunday, June 9, 2013 8:50:46 PM UTC-4, Steven Degutis wrote:
> But that's what I meant, that he's proposing we start with his lib and add
> extensibility in the places we want it. So my response to that still
> applies.
That's not at all what I said, proposed, alluded to, or anything of the
Is this still current? http://clojure.github.io/clojure-contrib/
On Sunday, June 9, 2013 8:19:15 PM UTC-5, Sean Corfield wrote:
>
> On Sun, Jun 9, 2013 at 5:50 PM, Steven Degutis
> >
> wrote:
> > Changing clojure.test seems like the wrong way to go. Being attached to
> a CA
> > makes it hard
No. Read http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go
On Sun, Jun 9, 2013 at 6:41 PM, Steven Degutis wrote:
> Is this still current? http://clojure.github.io/clojure-contrib/
>
> On Sunday, June 9, 2013 8:19:15 PM UTC-5, Sean Corfield wrote:
>>
>> On Sun, Jun 9, 2013 at 5:50
Then I apologize. I must have conflated what you said with what someone
else said. My mistake.
On Sunday, June 9, 2013 8:38:22 PM UTC-5, Jay Fields wrote:
>
> On Sunday, June 9, 2013 8:50:46 PM UTC-4, Steven Degutis wrote:
>
>> But that's what I meant, that he's proposing we start with his lib an
This may be a little off topic, but does this, or any other framework,
solve some testing inconveniences that exist in Clojure and probably other
functional languages:
1) testing recursive functions. I want to test what a recursion STEP does,
not the whole function. Can I mock 'recur'?
2) testin
Ooh, okay a little off topic here, but Expectations looks fantastic. Thanks
a lot Jay!
--
--
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 -
I sense a misunderstanding of transients in this message.
Am Sonntag, 9. Juni 2013 18:51:00 UTC+2 schrieb Steven Degutis:
>
> Thanks for the feedback. I'l look into #1. Regarding #2, we just wanted a
> side-effecty (mutable) way of adding assertion-results within a test. I
> suppose I could use
Jay,
2013/6/8 Jay Fields
> My favorite recent addition - I can run my app from within emacs, allowing
> me to change my app with a simple C-x C-e and see my changes immediately in
> the running app (no restart, refresh or reload necessary).
Would you mind to extend on that ?
How is this done
31 matches
Mail list logo
