Hi Colin,
there is much less naming-of-concepts. Clojure code tends to be much more
about the shape of transformations than the semantics of those
transformations.
yes, it seems to me that often (always maybe?) functional code speaks a lot
about HOW, and not much about WHAT
A case in
Some people use vars for seldom changing things. What do you think
about this VS atoms?
For example:
(declare ^:dynamic *server*)
(defn get-possibly-unbound-var [v]
(try (var-get v)
(catch Exception e
nil)))
(defn start-server! []
(if (get-possibly-unbound-var *server*)
That's right - idiomatic functional programming is very declarative
(from what I gather). Thanks for the references, and yes, I had
recognised the motivation that ;).
You ask Is the distinction between intention and implementation
considered unimportant, or not so important in functional
Yet another quick release - core.match 0.3.0-alpha4. The only change
is fixing a regression around the test sharing of literal patterns.
On Fri, Dec 12, 2014 at 12:54 PM, David Nolen dnolen.li...@gmail.com wrote:
core.match, an efficient pattern matcher for Clojure ClojureScript
New release
I think it would be great, and a very useful contribution to the Clojure
world, to have a flexible plotting library. My perspective, at risk of
going a bit off-topic, and from the biased position of a Gorilla REPL
author ...
When I think about the sort of programming I do as a scientist -
P.s. another compelling argument for a Clojure based ggplot alike emitting
SVG would be - assuming it was done so that it could be compiled with
ClojureScript - it would be a great addition to client-side plotting,
especially if it was wrapped to give a clean JS API as well.
--
You received
Multimethod dispatch based on Java classes is simply not reliable.
That sentence comes from a comment in a git commit related to an AOT fix
mentioned in a recent core.match announcement.
https://github.com/clojure/core.match/commit/0545c6af9d545dcf1bc0a3ca792771b9a678a030
(The workaround was
David,
- Stylistically, I found your naming conventions to be too verbose
yes, in the programming culture I am part of, long names are not frowned
upon when they help reveal intent.
I like the following diagram that J.B Rainsberger has put together on the
process of improving names:
Hi Leif,
if I write a function I only use once, I usually just inline it. Unless of
course I believe deep in my heart I'll have need of it somewhere else soon
So your motivation for the Extract Method
http://refactoring.com/catalog/extractMethod.html refactoring is sharing
of logic. There
I'm not sure about http-kit's streaming response implementation, but in
Aleph [1] if you use a stream/channel as a response body each message from
the stream will be immediately sent as an HTTP chunk.
Best,
Zach
[1] https://github.com/ztellman/aleph
On Saturday, December 6, 2014 9:03:41 AM
Hello,
Amazon is hiring for a Sr Engineer with experience in Clojure development.
Below is the description for our position. Please let me know if you, or
someone you may know would be interested in the position. The role is based
in our Headquarters in the South Lake Union neighborhood of
On Saturday, 13 December 2014 15:14:37 UTC+2, David Nolen wrote:
Yet another quick release - core.match 0.3.0-alpha4. The only change
is fixing a regression around the test sharing of literal patterns.
On Fri, Dec 12, 2014 at 12:54 PM, David Nolen dnolen.li...@gmail.com wrote:
core.match,
I'm not 100% sure and haven't really looked deeply at this comment or link
you mention, but perhaps this is related to
http://dev.clojure.org/jira/browse/CLJ-979.
This would only be the case for Clojure-dynamically generated Java classes
though, which is those from deftype or the macros built
TL:DR
Bardo https://github.com/pleasetrythisathome/bardo
https://github.com/pleasetrythisathome/bardo is a clojure(script) library
that provides semantics for defining interpolators between data structures as
well as utilities for composing them with each other, easing curves, and other
Yes sorry that commit should have been a bit more specific, the issue
is around deftype/defrecord generated classes.
David
On Sat, Dec 13, 2014 at 7:59 PM, Mike Rodriguez mjr4...@gmail.com wrote:
I'm not 100% sure and haven't really looked deeply at this comment or link
you mention, but
Excellent! :)
On Sat, Dec 13, 2014 at 8:16 PM, Dylan Butman dbut...@gmail.com wrote:
TL:DR
Bardo https://github.com/pleasetrythisathome/bardo is a clojure(script)
library that provides semantics for defining interpolators between data
structures as well as utilities for composing them with
Has the old invalid constant tag: -57 bug been fixed? I haven't run into
it in a while but I remember it cropping up occasionally when working with
older versions of Clojure, perhaps a year or two ago.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
Hi Leif,
I also favor a slightly less verbose style. A function is an abstraction,
and you seem to be writing functions for very concrete steps.
yes, in the programming culture I am part of, method extraction is quite
aggressive.
Here is Martin Fowler on the subject (in Refactoring,
Thanks for the feedback. I'll let you know how things progress.
Matthew
--
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
Hi Leif,
you just need to consolidate the more concrete steps. Something like:
flip-bottom-up - flip (or vertical- and horizontal-flip)
join-together-side-by-side - beside
put-one-on-top-of-the-other - stack (or ontop, or ...)
reverse-every-row - (map reverse rows) ; very readable to
Hi Leif,
if I compare your suggestion
(let [top-right (create-top-right-quadrant-for letter)
right (stack top-right
(flip top-right))
diamond (beside (map reverse (drop-first-col right)) right)]
(display diamond))
with mine
(let
21 matches
Mail list logo
