-
-
Notifications
You must be signed in to change notification settings - Fork 28
Fix #533 #534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #533 #534
Conversation
…RUE`) and for the fix of stan-dev#531, it is easier if separate `return_group_terms` cases do not exist, so remove that argument here
Tagging @aloctavodia. |
Could this just be combined with #532, or do you prefer to keep PRs more "atomic" as they handle slightly different issues? |
Co-authored-by: Osvaldo A Martin <aloctavodia@gmail.com>
They could be combined. I tend to prefer more atomic PRs, but I'm not sure if I always adhere to that principle myself 😄 In this case, I guess another motivation for different PRs was that I was a bit less sure if this fix here (in #534) is really correct, in the sense that it reflects @AlejandroCatalina's ideas when he implemented |
@aloctavodia what do you think, should I include this in #532? |
I think combining is fine in this case. |
Alright; done. Closing this PR now. |
Fixes #533 (how I would imagine it). This builds on top of branch
fix531
(from #532), so #532 should be merged first.