On 8/18/16, 9:43 AM, "Sonny To" <[email protected] on behalf of [email protected]> wrote: > However, out of desperation I fixed the warning > by renamed the functions that were overriding functions defined in core
You should be able to add (:refer-clojure :exclude [to-array hash]) to the ns form in the namespaces where those functions are defined (and used). > I do not know why but that fixed the problem. I have seen that with some of the new predicates introduced in Clojure 1.9.0 conflicting with certain functions in a few libraries (I ran into a problem like this with Encore until the maintainer added the appropriate refer/exclude). There are some situations where code that replaces core functions – which is what kaicode/tily is doing – can cause other code to fail. > functions in different namespace can have the same name even if it conflicts > with core That’s why we use namespace aliases and qualify references to such functions – but the namespace that _defines_ those functions should exclude the core functions (as above) and you should never refer them directly into another namespace (via :use or :refer :all or even :refer by name). Glad you got it working. Sean Corfield -- (970) FOR-SEAN -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/clojurescript.
