José Valim

> We could get more specific and pattern match on the message attributes The benefit of doing that is that, if there is a new format in the future, we...

Please go ahead @grevgeny! You can see the PRs from other clustering algorithms, to get an idea how of these contributions usually work (and the project goals).

We don't need to deprecate, we can just rename the module. It should be easy for anyone to just rename it accordingly. :)

Hi @krstopro, I want to release a new version soon. If we plant to remove `Scholar.Neighbors.KNearestNeighbors`, it would be better to do it before, so we update the docs accordingly?

We would also need to mirror those decisions on top of `RadiusNearestNeighbors`.

Perfect. KNN is the most important, Radius can be done later. :)

Thank you @krstopro! I will work on #265 and @msluszniak will update the notebooks. :) Once KNNRegression is ready, we can release a new version!

You can use main for now.

Errr, wrong issue.

At the same time, I am not sure if there is something to unify here? I think checking for shapes should be done per module, as they can provide better...