Writing the code

All the code developed for the new optimizer will go in a file namedR/opt-**optimizer-name**.R.

An optimizer will be a single function (one exported), which should be calledopt_**optimizer_name**. This function will take as input atexts parameter that contains a string list (character vector) with the code to optimize. An example of this, with just one code to optimize, would be:

texts<-list(paste("i <- 320 * 200 * 32","x <- i * 20 + 100",    sep="\n"))

All other parameters that the functionopt_**optimizer_name** takes as input must have an associated default parameter, for example,opt_**optimizer_name** <- function(texts, param1 = FALSE) { ... }.

As output, the developed function must return a list with a fieldcodes that must have the same format as thetexts input but with the code optimized.

To document code we use theroxygen2 package. You should give a brief description of the new optimizer, of the input parameters, and an example of use.

As skeleton to use to develop the new optimizer we propose to follow:

#' Optimizer: **New Optimizer Name**#'#' **New optimizer description**#' Carefully examine the results after running this function!#'#' @param texts A list of character vectors with the code to optimize.#' **Other parameters description**#'#' @examples#' **New optimizer example of use**#'#' @export#'opt_**optimizer_name**<-function(texts) {# todo: **list of possible improvements for the optimizer**  res<-list()**new optimizer code**  res$codes<-**...**return(res)}

For the parsing and tokenization of the code we suggest to use the functions developed inR/parse.R.

Writing the tests

For testing, we use thetestthat package. All the code for testing the new optimizer will go in a file namedtests/testthat/test-opt_**optimizer_name**.R.

Please create a test suite that covers a large percentage of possible use and border cases.

As skeleton to use to develop the new optimizer’s test suite we propose to follow:

context("opt_**optimizer_name**")test_that("**test name**", {**...**})**more test cases**

Writing the vignette

When developing a new optimizer, we create a vignette to explain it. This documentation will not only be a vignette of the package but will also be part of therco website.

For writing vignettes, we use theknitr andrmarkdown packages. The new vignette will go in a file namedvignettes/opt-**optimizer-name**.Rmd, and must follow the skeleton:

---output: rmarkdown::html_vignettetitle:**New Optimizer Name**vignette:>  %\VignetteIndexEntry{**New Optimizer Name**}  %\VignetteEngine{knitr::rmarkdown}  %\VignetteEncoding{UTF-8}---# **New Optimizer Name**## Background## Example## Implementation## **Additional headings** (optional)## To-Do (optional)

TheBackground section must introduce the reader to why this optimization provides improvements, and what it does. TheExample section must give a real example to be optimized, and show the improvements it gave in terms of execution speed, memory usage, or others. TheImplementation section must show the idea beneath the optimizer coding, this section intends to ease the understanding of the developed code if it is needed to be edited or improved. Then, as many sections as necessary can be included, where questions and challenges related to the optimizer are explained or commented. Finally, if a list of possible improvements for the optimizer were detailed, each of them should be discussed in theTo-Do section.

Writing additional files

# rco **x.y.(z+1)**- Adding**New Optimizer Name** optimizer.**...**