How should we document methods that have different arguments than the default method?

[nikosbosse]

In #790 @seabbs introduced the functions as_point() and as_quantile() which transform a forecast object into an object of class forecast_point() and forecast_quantile(), respectively.

For other methods (e.g. score() or is_forecast()) we always lumped all methods into one doc by using @rdname generic_function. This was fine, as all methods had the same arguments.

In this case, the methods have different arguments, depending on the class of the input.

Should all methods appear in one manual page, or should they appear in different ones?

I.e. should we have something like this

Or something like this

and a separate

[seabbs]

IMO they should appear in different ones. In your first example all the args for all the methods get lumped together in a very confusing way