Hello! I'm student and I'm finishing the 4-year university studying
(baccalaureate). I'm not from English-talking country but, you see, my
text-speech is pretty understandable. I'm improving my spoken English also.
I'm writing my diploma in Clojure and I really like this language. But
there's n
Why does `clojure.lang.RT/canSeq` need to check both `ISeq` _and_ `Seqable`
when `ISeq <- IPersistentCollection <- Seqable`?
static public boolean canSeq(Object coll){
return coll instanceof ISeq
|| coll instanceof Seqable
|| coll == null
|| coll instanceof
On Tuesday, May 2, 2017 at 7:34:21 PM UTC-7, Alex Miller wrote:
>
>
> On Tuesday, May 2, 2017 at 6:00:52 PM UTC-5, Jenny Finkel wrote:
>>
>> Thanks for the reply. Your explanation for why it should be expected
>> sounds like implementation details though (why it is that way, but not why
>> it s
On Tuesday, May 2, 2017 at 6:00:52 PM UTC-5, Jenny Finkel wrote:
>
> Thanks for the reply. Your explanation for why it should be expected
> sounds like implementation details though (why it is that way, but not why
> it should be that way).
>
I'll grant you that, and I could certainly be wrong
Thanks for the reply. Your explanation for why it should be expected sounds
like implementation details though (why it is that way, but not why it
should be that way). The docstring for 'pr' admittedly makes a reference to
"by default" ("Prints the object(s) to the output stream that is the
cur
The `pr` family of functions prints data as readable data by default (with
*print-readably* defaulted to true - this happens in RT).
The `print` family of functions wraps the `pr` family and turns off this
behavior by binding *print-readably* to nil.
So I think when surrounding a pr with a pr
Expressed without the interaction of dynamic bindings and laziness (which is
why there’s the difference here), the question boils down to whether this is
the correct, expected behavior or not:
boot.user=> (pr-str ["a" "b"])
"[\"a\" \"b\"]"
boot.user=> (binding [*print-readably* nil] (pr-str
Correct. "The reason is that print binds *print-readably* to nil, whereas
pr-str does not bind it to true, even though I believe it should."
On Tuesday, May 2, 2017 at 1:55:04 PM UTC-7, Justin Smith wrote:
>
> there's something going on with dynamic bindings here
>
> peregrine.circle=> (let [xs (
there's something going on with dynamic bindings here
peregrine.circle=> (let [xs (map #(pr-str %) ["a" "b"])] (println xs))
(a b)
nil
peregrine.circle=> (let [xs (doall (map #(pr-str %) ["a" "b"]))] (println
xs))
("a" "b")
nil
On Tue, May 2, 2017 at 1:55 AM Paulus Esterhazy
wrote:
> Looks lik
"Do you have experience with modern web stacks? Are you familiar with or
keen on learning functional programming? Have you architected modular
front-end solutions? We're always looking for and exploring new tools and
technologies to find the best fit for the problem at hand, and now we are
seek
Looks like a bug to me. ClojureScript doesn't seem to have this problem.
On Tue, May 2, 2017 at 7:50 AM, Jenny Finkel wrote:
> Hello!
>
> I think I may have found a bug in clojure. When pr-str is called from within
> print, it doesn't produce a read-string-able string. Here is a simple
> example:
11 matches
Mail list logo
