I've been stung by this too. One work around I use is *(:refer-clojure
:exclude [/])* and *(:require [some.ns :refer [/])* in my *ns* form. Then
refer to *clojure.core//* directly if needed. It's good to hear this will
be fixed in 1.6.
On Tuesday, July 30, 2013 5:26:23 AM UTC-7, Maik Schünemann
Thanks Nicola!
On Tue, Jul 30, 2013 at 2:32 PM, Nicola Mometto wrote:
>
> It's going to be possible in clojure-1.6 see:
> https://github.com/clojure/clojure/commit/88cad2510243289d2bbe28cf8bd14007d9df5fc3
>
> Maik Schünemann writes:
>
>> Is / a valid clojure function name (valid, but not recomme
It's going to be possible in clojure-1.6 see:
https://github.com/clojure/clojure/commit/88cad2510243289d2bbe28cf8bd14007d9df5fc3
Maik Schünemann writes:
> Is / a valid clojure function name (valid, but not recommended)?
> I tought so because of clojure.core//
> in the repl there is also no prob
Is / a valid clojure function name (valid, but not recommended)?
I tought so because of clojure.core//
in the repl there is also no problem with clojure.core//:
clojure.core//
;=>#
but if / is in another namespace, for example in core.matrix:
clojure.core.matrix.operators//
RuntimeException Invalid