We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In dataset.clj before that commit,
dataset.clj
the function new-col was re-exported twice, probably by mistake.
new-col
tech.ml.dataset/src/tech/v3/dataset.clj
Line 56 in fddeddc
Line 213 in fddeddc
so the second one "won".
After the change, only the first one stayed, having a different arrity and probably doing something different as well.
So any code using tech.ml.dataset.new-column before b6f9f4e will stop compiling when moving to b6f9f4e + 1.
tech.ml.dataset.new-column
:at [clojure.lang.Compiler$InvokeExpr eval Compiler.java 3711]} {:type clojure.lang.ArityException :message Wrong number of args (2) passed to: tech.v3.dataset/new-column :at [clojure.lang.AFn throwArity AFn.java 429]}]
As this is in the main namespace it might affect some people.
The text was updated successfully, but these errors were encountered:
Great catch thanks a lot for tracking this down.
Sorry, something went wrong.
54143b4
No branches or pull requests
In
dataset.clj
before that commit,the function
new-col
was re-exported twice, probably by mistake.tech.ml.dataset/src/tech/v3/dataset.clj
Line 56 in fddeddc
tech.ml.dataset/src/tech/v3/dataset.clj
Line 213 in fddeddc
so the second one "won".
After the change, only the first one stayed, having a different arrity and probably doing something different as well.
So any code using
tech.ml.dataset.new-column
before b6f9f4e will stop compilingwhen moving to b6f9f4e + 1.
As this is in the main namespace it might affect some people.
The text was updated successfully, but these errors were encountered: