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
@paul-buerkner I'd like to add a generic for reloo so we can have reloo.stanreg and reloo.brmsfit methods. But I see that currently brms takes the first argument of reloo to be the loo object. So it can't change to a brmsfit method without breaking backwards compatibility, right? If that's the case then maybe we should use a different name than reloo for the generic and new methods and you can deprecate reloo it in brms. What do you think? Definitely open to other ideas.
The text was updated successfully, but these errors were encountered:
I could just add a reloo.loo method to brms or we can even add it to loo and then internally do the dispatch based on the second, model object argument. This way, we won't break backwards compatibility but still get the generic going I think.
@paul-buerkner I'd like to add a generic for
reloo
so we can havereloo.stanreg
andreloo.brmsfit
methods. But I see that currently brms takes the first argument ofreloo
to be the loo object. So it can't change to a brmsfit method without breaking backwards compatibility, right? If that's the case then maybe we should use a different name thanreloo
for the generic and new methods and you can deprecatereloo
it in brms. What do you think? Definitely open to other ideas.The text was updated successfully, but these errors were encountered: