Suggest you look at dplyr::mutate as this functionality is widely used
there and has shown itself to be useful.
On Tue, Aug 27, 2024 at 9:16 AM Sebastian Meyer wrote:
>
> Am 27.08.24 um 11:55 schrieb peter dalgaard:
> > Yes. A quirk, rather than a bug I'd say. One issue is that the internal
> >
Am 27.08.24 um 11:55 schrieb peter dalgaard:
Yes. A quirk, rather than a bug I'd say. One issue is that the internal logic
of transform() relies on
e <- eval(substitute(list(...)), `_data`, parent.frame())
tags <- names(e)
so untagged entries in ... will not be included.
... unless
It could be enhanced to handle data frame argos. Unnamed args are
currently just ignored so adding such would be backwards compatible.
Any interest in this?
On Tue, Aug 27, 2024 at 5:55 AM peter dalgaard wrote:
>
> Yes. A quirk, rather than a bug I'd say. One issue is that the internal logic
>
Yes. A quirk, rather than a bug I'd say. One issue is that the internal logic
of transform() relies on
e <- eval(substitute(list(...)), `_data`, parent.frame())
tags <- names(e)
so untagged entries in ... will not be included. The other part is a direct
consequence of a quirk in data.fr
Kurt Hornik wrote:
>>ernesto writes:
>>
>>
>
>
>
>>Hi,
>>
>>
>
>
>
>>I'm adjusting package FLCore to the new R version and I got an error
>>due to the change of the transform function argument "x" to
>>"_data". Was this intentional ?
>>
>>
>
>You mean that you
> ernesto writes:
> Hi,
> I'm adjusting package FLCore to the new R version and I got an error
> due to the change of the transform function argument "x" to
> "_data". Was this intentional ?
You mean that you get the error? :-)
See NEWS:
o The data frame argument to transform() is n
