Anthony Blaom, PhD

Thanks for the feedback! Others have criticised the adoption of the "MLJ" prefix for packages that are really meant for more general consumption. (MLJScientificTypes is a case in point -...

@giordano I'm not sure I understand. MLJSerialization is not intended to be independent of MLJBase, so it can just import `Machine`, no? We could avoid type piracy by not importing...

Also, one may want to specify per-dimension weights, eg for weighting time series forecasts differently depending on how far in future the forecast is.

Note that user-defined measures are a temporary workaround. See one suggestion posted [here](https://github.com/alan-turing-institute/MLJ.jl/issues/800#issue-917469684)

The target `y` in `X, y = @load_boston` is a view of an array not an `Array`.

For selecting rows, I'm hoping https://github.com/JuliaData/Tables.jl/pull/278 will be more helpful, as it allows individual Tables formats to expose more efficient selection methods to the generic Tables.jl API, which TableOperations.jl cannot...

Worth noting here that, as far as I know, `selectcols` is not used within MLJBase at all, only `selectrows`. However, I believe it is exposed in MLJModelInterface, and the transformers...

Well, this is going to take a while. But I do think 21 consecutive patch releases is sign that we should probably start this.

Just a short response for now. The `dropmissing` functionality already exists in julia, no? ```julia julia> y = [1.0, 2.0, missing][1:2] 2-element Array{Union{Missing, Float64},1}: 1.0 2.0 julia> skipmissing(y) |> collect...

I agree this requires a little thought. Let's flag this issue for discussion at next meeting. Of course input welcome in the meantime.