rco
rco copied to clipboard
jcrodriguez1989
Package: The R Code Optimizer
These are valid R expressions, they are parsed differently, and not being well-handled by rco. ```r `sum1`
When trying to optimize `jagsTwoBaselinesFull.R` file from the `tRophicPosition` package, I noticed that `utils::getParseData` truncates long strings to a string like `"[2001 chars quoted with '\"']"`. This bug is related...
I think it would be nifty to be able to create a report out of `{rco}` optimisers. The idea would be to analyse the whole code and return some kind...
Based on the specifications provided [here](https://rpubs.com/IACCancu/462502), I've added the opt-column-extractor.R file as part of the [hard test](https://github.com/rstats-gsoc/gsoc2020/wiki/rco%3A-The-R-Code-Optimizer#solutions-of-tests) along with relevant tests and vignette.
In response to the review of my PR [here](https://github.com/jcrodriguez1989/rco/pull/147), I have opened this PR from an alternative branch of my forked repository(not the master). 1. All the mentioned failed test...
If within a function, a variable is assigned multiple times, but just the last assignation is read, then the optimizer could keep just the last one. For example: ```r foo
The optimizer is currently eliminating any dead expression, however, the code: ```r foo
The following code snippet: ~~~R library(rco); code1
Woud be nice to have a custom print method: Current: ``` r code