You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
In #790 @seabbs introduced the functions
as_point()
andas_quantile()
which transform a forecast object into an object of classforecast_point()
andforecast_quantile()
, respectively.For other methods (e.g.
score()
oris_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
The text was updated successfully, but these errors were encountered: