You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Excerpts from a conversation on Clojurians Slack channel #clojure-dev on 2018-Sep-05:
"I had an issue where I had two functions in a file, replace-_ and replace_-. This worked in dev, but when I aot the project, any invocation of either is replaced by the last one in the file. I suppose this is because munge gives the same result for both those names."
"The clojure names of the fns are foo.common.core/replace-_ (and replace_-). The class in the jar is /foo/common/core$replace__.class"
Eastwood already issues a warning when def'ing the same name twice. A new check could be implemented as a variation of that one. If so, it would probably be best to name it differently than the current one, so they could be turned on/off independently of each other.
The text was updated successfully, but these errors were encountered:
Excerpts from a conversation on Clojurians Slack channel #clojure-dev on 2018-Sep-05:
"I had an issue where I had two functions in a file,
replace-_
andreplace_-
. This worked in dev, but when I aot the project, any invocation of either is replaced by the last one in the file. I suppose this is becausemunge
gives the same result for both those names.""The clojure names of the fns are
foo.common.core/replace-_
(andreplace_-
). The class in the jar is/foo/common/core$replace__.class
"Eastwood already issues a warning when def'ing the same name twice. A new check could be implemented as a variation of that one. If so, it would probably be best to name it differently than the current one, so they could be turned on/off independently of each other.
The text was updated successfully, but these errors were encountered: