Davis Vaughan

`morph()` would have to work like `summarise()` currently works, I think. i.e. each group computation can return any number of rows, and we recycle the per group results "rowwise" across...

I'm remembering that tidygraph uses `morph()`, which might be enough to prevent us from using it. I also thought of `restructure()`, which is kind of nice because it is closer...

Or just `build()`, i.e. "build a new data frame from an existing one", if we aren't worried about conflicting with `devtools::build()` that sounds pretty good

I cannot reproduce any issue here. Both of your examples run without error for me. I ran both examples with reprex and interactively, and each time I got the same...

I see what you are saying @wa2003. Normally I would suggest `tq_mutate_xy()` for this kind of thing, but the `x` argument only takes 1 column at a time and you...

@mdancho84 I see what @gmahjub is saying. We intentionally turn `OHLC = FALSE` when `to.period` is used in `tq_mutate`. There were a few reasons for this, I think one of...

@apsteinmetz, looks good. As to your comments about from/to, you should be able to pass either: - `from`/`to` as character vectors - `start.date`/`end.date` as proper Dates Internally we translate `from`/`to`...

I don't think you can do this easily, but you can probably use `period.apply()` with a custom INDEX that corresponds to weeks that end on Fridays. https://www.rdocumentation.org/packages/xts/versions/0.10-2/topics/period.apply

Anecdotal conversation with CRAN that can guide some of this: We sent in a workflows submission with 3 known breakages. This was `cran-comments.md`: ``` ## revdepcheck results We checked 28...

See also https://github.com/r-lib/rlang/pull/1401 I do think it would be useful. We didn't add it to rlang immediately because we thought we might need some kind of dependency system (i.e. `compat-foo.R`...