shinnar
we plan to create a new `export_to_sklearn` function on Operator. `export_to_sklearn_pipeline` will just call it and be deprecated / removed subject to compatibility constraints.
This should include tests for the expected format of the return value from the summary method
I am fine with this, if someone (@jeromesimeon?) is interested in implementing it. In theory, it is reasonable, and can be implemented in Coq along the lines you suggest. In...
This problem is not restricted to things like this -- it appears that every time we suffix with a number we do so only on the declaration, not on the...
Actually, looking into this more resulted in noticing #82 as well
to be clear, we are talking about free variables here. I think the fix here is to - avoid emitting duplicate let bindings for the same free variable. - stop...
4ae6a5f addresses the duplication problem.
97e51e4 fixes this particular example (almost as a side-effect), since the variable is first rewritten to "c$" as part of the let (which is a bit hacky, incidentally). However, the...
we currently are prepending "v" (and now "vc$") to our emitted variables, but we check for javascript keyword conflicts with the un-prepended version. So it complains about "this", but not...