It would be fun to use core.match to have an easier time testing results
that are hash-maps of different patterns. I'm just having a difficult time
to get failing cases' input values show up in test results:
(use 'clojure.test)
(require '[clojure.core.match :refer [match]])
(defmacro matches
I thought about writing a cljs port, but I don't write much cljs so I
thought better of it. Software quality usually suffers when it isn't used
by the author, I think.
I'd love to find a collaborator to work on the cljs port of this library.
ES6 actually adds string.prototype.normalizer but
That's ++great, Lars! Would you be open to convert this into CLJC so
it can all be used from CLJS as well? I guess the main stumbling block
is the use of java.text.Normalizer in strip-accents, but that could be
replaced with a hardcoded regexp solution for CLJS...
Thanks!
On 21 June 2015 at
Mike (core.matrix author) has been adjusting the API according to his needs
and those of other users. I don't think anyone will disagree with the
statement that good APIs are shaped by usage and keeping things simple.
That said, I see no reason why there shouldn't be a common API which is
The troubling thing isn't the use of Normalizer to remove accents, but the
use of .toUpper, .toLower, and .equalsIgnoreCase instead of Normalizer,
which may run into problems. For example you probably want weiß and
WEISS to compare equal when ignoring case. For a case-insensitive
comparison I
I'm happy to announce the first release of superstring, a string
manipulation library for clojure.
Read more about why I wrote superstring here:
https://github.com/expez/superstring
Or check out the api docs for a quick overview of what's provided:
I'm not sure I agree that it would make sense, in general, for WEISS and
weiß to be considered equal when ignoring case. I don't write any
german, so I might be wrong on that, though. Thankfully I didn't have to
write my own case-insensitive string comparison code because Oracle already
Do you know about cuerdas? https://github.com/funcool/cuerdas
It is already compatible with clojure and clojurescript ;)
On Sun, Jun 21, 2015 at 5:05 PM, Karsten Schmidt i...@toxi.co.uk wrote:
That's ++great, Lars! Would you be open to convert this into CLJC so
it can all be used from CLJS as
Thanks, guys! Just pushed another update: 0.0.881 with a few additions
to the viz module updated examples:
Heatmap visualizations (incl. custom cell shapes):
https://github.com/thi-ng/geom/blob/master/geom-viz/src/core.org#heatmap
GIS terrain elevation example:
Hi,
We've been trying out RC2 in production with no issues to report. (The last
hiccup we had was back with CLJ-1738 - Seqs over Java iterators but have
since reworked the offending Java iterators.)
Cheers,
Ted
On Thursday, June 18, 2015 at 3:44:39 AM UTC+10, Alex Miller wrote:
Clojure
As it sounds a lot like your definition of OOP to me.
For sure, this code relies on messages passing. It is functional in the
old sense that the messages are functions -- a usage of the word
functional that any Lisper would have understood for decades. But it is
not functional in the
On Saturday, 20 June 2015 08:43:39 UTC+1, Dragan Djuric wrote:
On Friday, June 19, 2015 at 11:17:02 PM UTC+2, Christopher Small wrote:
I see now Dragan; you're concerned not about whether easily implementing
and swapping in/out implementations of core.matrix is possible, but whether
it can
I'd like to see an example of this functional worker style you mention.
As it sounds a lot like your definition of OOP to me. Not to mention that
anything that talks to a queue is performing io and is therefore not
functionally pure. So it sounds like you went and re-built component, but
this time
How about this:
(defmacro matches [value pattern]
`(is (match ~value ~pattern true :else false)
(str (match ~value '~pattern
(let [a {:x 2}]
(matches a {:y _}))
; = FAIL
; = (match {:x 2} {:y _})
; = expected: (clojure.core.match/match a {:y
There are ways to handle dependencies without going down the OOP route that
Stuart Sierra took. However, there are a lot of good ideas in Stuart
Sierra's Component library, and to the extent that you can borrow those
ideas, you end up with code that resembles best practice in the Clojure
Often compatibility comes at the cost of functionality and maintainability,
so in the end of the day someone has to pay the piper. Why would anyone be
using Emacs 23? It's easy to upgrade it pretty much everywhere and I doubt
anyone is doing much programming on their RHEL 5/6 production servers.
Hi all,
Since the last leiningen release insists on using nREPL 0.2.6, i
thought i'd have a go at using boot with CIDER instead.
From what i can tell, boot has a similar issue to leiningen, in
that the contents of ~/.boot/build.boot aren't respected by the
boot REPL unless one starts the
Did you go through this https://github.com/boot-clj/boot/wiki/Cider-REPL ?
On 21 June 2015 at 11:20, Alexis flexibe...@gmail.com wrote:
Hi all,
Since the last leiningen release insists on using nREPL 0.2.6, i thought
i'd have a go at using boot with CIDER instead.
From what i can tell,
Bozhidar Batsov bozhi...@batsov.com writes:
Did you go through this
https://github.com/boot-clj/boot/wiki/Cider-REPL ?
No i did not; sorry. :-( i keep forgetting to check if a GitHub
project actually makes use of the GH wiki functionality! Following
the instructions on that page got
19 matches
Mail list logo
