+1
On Tue, Jul 19, 2016 at 10:35 AM, Jacob Strength wrote:
> This looks great! I was just curious though, what are the advantages of
> this over say the Clojure page on reddit? To me it seems very similar.
>
>
> On Friday, July 15, 2016 at 9:28:12 AM UTC-6, Ertuğrul Çetin
One of the best and instructive post I have read in years. Thanks Timothy
Mimmo
> Il giorno 23 lug 2016, alle ore 22:26, Timothy Baldridge
> ha scritto:
>
> Peter,
>
> I share your frustration, or at least I did at one point. If you dig back
> about 6 years in this
Peter,
I share your frustration, or at least I did at one point. If you dig back
about 6 years in this mailing list you will find an epic rant by me about
OpenGL and Clojure. Looking back on what I thought at that time, I'll
mention as perhaps they can help you not make the mistakes I did.
1) Be
What prohibition?
user=> {}
{}
user=> [:a]
[:a]
user=> 1
1
user=> (assoc-in *3 *2 *1)
{:a 1}
- James
On 23 July 2016 at 18:45, Michael Rice wrote:
> Why the prohibition?
>
> Michael
>
> --
> You received this message because you are subscribed to the Google
> Groups
Why the prohibition?
Michael
--
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
If they are all in one namespace, you can use `ns-publics` on that
namespace ... e.g. `(ns-publics 'user)`.
On Sat, Jul 23, 2016 at 5:28 AM, Cecil Westerhof
wrote:
> For a project I define some extra functions if it is started in the REPL.
> I like to know which extra
Abstractions and dynamic/static typing are orthogonal. Static/dynamic
is simply _when_ types are considered. Strong/weak typing is arguably
more relevant and is about how narrowly type information is
considered.
I can't find an actual declaration but I consider Clojure is dynamic
but strongly
thanks,
wade
> On Jul 23, 2016, at 6:57 AM, Colin Yates wrote:
>
> As James said it is correct, but maybe not intuitive. Intuitively we
> think an integer isn't empty, but actually it is a non-sensical
> question - Integers can no more be empty than they can be full.
>
The point is that an 'Integer'
> (abstraction) has no sense of 'emptiness' or 'fullness'.
>
> IMHO that might be true for a statically typed language, but in the case
of a dynamic language like Clojure it makes perfect sense, and most users
expect
this behavior.
--
You received this
As James said it is correct, but maybe not intuitive. Intuitively we
think an integer isn't empty, but actually it is a non-sensical
question - Integers can no more be empty than they can be full.
I noticed that Clojure's use of abstractions, and sticking to those
abstractions is far greater than
You are not alone - it's the number one frustration in the community
https://www.reddit.com/r/Clojure/comments/433y02/state_of_clojure_2015_survey_results/
But also see the responses - maybe we will have some major improvements
with 1.9. Spec looks like good infra to support those efforts for
For a project I define some extra functions if it is started in the REPL. I
like to know which extra functions there are in the REPL, so at the moment
I am doing the following:
(print (str "Defined REPL functions:\n"
"- do-show-schemas\n"
"- do-show-table
12 matches
Mail list logo