Matthew Kay

Followup question: how many unique values of `item` are there here: `spread_draws(stanfit, cutpoint[item], dispersion[item])`? And secondary followup question: how fast is `spread_draws(stanfit, cbind(cutpoint, dispersion)[item])`?

Followup: I think I've narrowed this problem to `tidy_draws()`, but if you have time for a quick check on your end it might help me be sure (and could give...

> Belatedly, yes I can confirm that spreading is waaay faster with the tidy draws saved ahead of time at this, even when I take a large number of samples....

This is good timing --- I am currently working on some changes to make it easier to deal with matrices in spread_draws / gather_draws. Something I am currently implementing is...

Okay, cool. Since `gather_draws` is using the names you provide in the call to determine the column names in the output (and also to automatically do joins if you ask...

Great, glad that helps! W.r.t. coming up with a solution that doesn't require the extra call to `recover_types`, one option might be to make it so that duplicated columns names...

Makes sense. Okay, perhaps a sensible solution is approach 1 + approach 4 to make more flexible cases possible through explicit renaming. So TODO: - [ ] make repeat uses...

or maybe "grid -> condition -> munge -> map"

You should be able to handle this using the `sep` argument to `spread_draws()` / `gather_draws()`. Something like `spread_draws(..., sep = ", ")` should do it, or if the presence of...

Good point that the error when a spec breaks could suggest use of `sep`. TODOs for my benefit: - [ ] consider changing default of `sep` arg to something like...