# 14 Expressions

## Prerequisites

To capture and compute on expressions, and to visualise them, we will load the rlang^{24} and the lobstr^{25} packages.

## 14.1 Abstract syntax trees

**Q1**: Reconstruct the code represented by the trees below:

```
#>
[33m█
[39m─
[1m
[35mf
[39m
[22m
#> └─
[33m█
[39m─
[1m
[35mg
[39m
[22m
#> └─
[33m█
[39m─
[1m
[35mh
[39m
[22m
#>
[33m█
[39m─
[1m
[35m`+`
[39m
[22m
#> ├─
[33m█
[39m─
[1m
[35m`+`
[39m
[22m
#> │ ├─1
#> │ └─2
#> └─3
#>
[33m█
[39m─
[1m
[35m`*`
[39m
[22m
#> ├─
[33m█
[39m─
[1m
[35m`(`
[39m
[22m
#> │ └─
[33m█
[39m─
[1m
[35m`+`
[39m
[22m
#> │ ├─
[1m
[35mx
[39m
[22m
#> │ └─
[1m
[35my
[39m
[22m
#> └─
[1m
[35mz
[39m
[22m
```

**A**: Let the source (of the code chunks above) be with you and show you how the ASTs (abstract syntax trees) were produced.

```
ast(f(g(h())))
#> █─f
#> └─█─g
#> └─█─h
ast(1 + 2 + 3)
#> █─`+`
#> ├─█─`+`
#> │ ├─1
#> │ └─2
#> └─3
ast((x + y) * z)
#> █─`*`
#> ├─█─`(`
#> │ └─█─`+`
#> │ ├─x
#> │ └─y
#> └─z
```

**Q2**: Draw the following trees by hand then check your answers with `ast()`

.

```
f(g(h(i(1, 2, 3))))
f(1, g(2, h(3, i())))
f(g(1, 2), h(3, i(4, 5)))
```

**A**: Let us delegate the drawing to the lobstr package.

```
ast(f(g(h(i(1, 2, 3)))))
#> █─f
#> └─█─g
#> └─█─h
#> └─█─i
#> ├─1
#> ├─2
#> └─3
ast(f(1, g(2, h(3, i()))))
#> █─f
#> ├─1
#> └─█─g
#> ├─2
#> └─█─h
#> ├─3
#> └─█─i
ast(f(g(1, 2), h(3, i(4, 5))))
#> █─f
#> ├─█─g
#> │ ├─1
#> │ └─2
#> └─█─h
#> ├─3
#> └─█─i
#> ├─4
#> └─5
```

**Q3**: What’s happening with the ASTs below? (Hint: carefully read `?"^"`

)

```
ast(`x` + `y`)
#> █─`+`
#> ├─x
#> └─y
ast(x ** y)
#> █─`^`
#> ├─x
#> └─y
ast(1 -> x)
#> █─`<-`
#> ├─x
#> └─1
```

**A**: ASTs start function calls with the name of the function. This is why the call in the first expression is translated into its prefix form. In the second case, `**`

is translated by R’s parser into `^`

. In the last AST, the expression is flipped when R parses it:

**Q4**: What is special about the AST below? (Hint: re-read section 6.2.1)

```
ast(function(x = 1, y = 2) {})
#> █─`function`
#> ├─█─x = 1
#> │ └─y = 2
#> ├─█─`{`
#> └─<inline srcref>
```

**A**: The last leaf of the AST is not explicitly specified in the expression. Instead, the `srcref`

attribute, which points to the functions source code, is automatically created by base R.

**Q5**: What does the call tree of an `if`

statement with multiple `else if`

conditions look like? Why?

**A**: The AST of nested `else if`

statements might look a bit confusing because it contains multiple curly braces. However, we can see that in the `else`

part of the AST just another expression is being evaluated, which happens to be an `if`

statement and so forth.

```
ast(
if (FALSE) {
1
} else if (FALSE) {
2
} else if (TRUE) {
3
}
)
#> █─`if`
#> ├─FALSE
#> ├─█─`{`
#> │ └─1
#> └─█─`if`
#> ├─FALSE
#> ├─█─`{`
#> │ └─2
#> └─█─`if`
#> ├─TRUE
#> └─█─`{`
#> └─3
```

We can see the structure more clearly if we avoid the curly braces:

```
ast(
if (FALSE) 1
else if (FALSE) 2
else if (TRUE) 3
)
#> █─`if`
#> ├─FALSE
#> ├─1
#> └─█─`if`
#> ├─FALSE
#> ├─2
#> └─█─`if`
#> ├─TRUE
#> └─3
```

## 14.2 Expressions

**Q1**: Which two of the six types of atomic vector can’t appear in an expression? Why? Similarly, why can’t you create an expression that contains an atomic vector of length greater than one?

**A**: There is no way to create raws and complex atomics without using a function call (this is only possible for imaginary scalars like `i`

, `5i`

etc.). But expressions that include a function are *calls*. Therefore, both of these vector types cannot appear in an expression.

Similarly, it is not possible to create an expression that evaluates to an atomic of length greater than one without using a function (e.g. `c()`

).

Let’s make this observation concrete via an example:

```
# Atomic
is_atomic(expr(1))
#> [1] TRUE
# Not an atomic (although it would evaluate to an atomic)
is_atomic(expr(c(1, 1)))
#> [1] FALSE
is_call(expr(c(1, 1)))
#> [1] TRUE
```

**Q2**: What happens when you subset a call object to remove the first element, e.g. `expr(read.csv("foo.csv", header = TRUE))[-1]`

. Why?

**A**: When the first element of a call object is removed, the second element moves to the first position, which is the function to call. Therefore, we get `"foo.csv"(header = TRUE)`

.

**Q3**: Describe the differences between the following call objects.

```
x <- 1:10
call2(median, x, na.rm = TRUE)
call2(expr(median), x, na.rm = TRUE)
call2(median, expr(x), na.rm = TRUE)
call2(expr(median), expr(x), na.rm = TRUE)
```

**A**: The call objects differ in their first two elements, which are in some cases evaluated before the call is constructed. In the first one, both `median()`

and `x`

are evaluated and inlined into the call. Therefore, we can see in the constructed call that median is a generic and the `x`

argument is 1:10.

```
call2(median, x, na.rm = TRUE)
#> (function (x, na.rm = FALSE, ...)
#> UseMethod("median"))(1:10, na.rm = TRUE)
```

In the following calls we remain with differing combinations. Once, only `x`

and once only `median()`

gets evaluated.

```
call2(expr(median), x, na.rm = TRUE)
#> median(1:10, na.rm = TRUE)
call2(median, expr(x), na.rm = TRUE)
#> (function (x, na.rm = FALSE, ...)
#> UseMethod("median"))(x, na.rm = TRUE)
```

In the final call neither `x`

nor `median()`

are evaluated.

Note that all these calls will generate the same result when evaluated. The key difference is when the values bound to the `x`

and `median`

symbols are found.

**Q4**: `rlang::call_standardise()`

doesn’t work so well for the following calls.
Why? What makes `mean()`

special?

```
call_standardise(quote(mean(1:10, na.rm = TRUE)))
#> mean(x = 1:10, na.rm = TRUE)
call_standardise(quote(mean(n = T, 1:10)))
#> mean(x = 1:10, n = T)
call_standardise(quote(mean(x = 1:10, , TRUE)))
#> mean(x = 1:10, , TRUE)
```

**A**: The reason for this unexpected behaviour is that `mean()`

uses the `...`

argument and therefore cannot standardise the regarding arguments. Since `mean()`

uses S3 dispatch (i.e. `UseMethod()`

) and the underlying `mean.default()`

method specifies some more arguments, `call_standardise()`

can do much better with a specific S3 method.

```
call_standardise(quote(mean.default(1:10, na.rm = TRUE)))
#> mean.default(x = 1:10, na.rm = TRUE)
call_standardise(quote(mean.default(n = T, 1:10)))
#> mean.default(x = 1:10, na.rm = T)
call_standardise(quote(mean.default(x = 1:10, , TRUE)))
#> mean.default(x = 1:10, na.rm = TRUE)
```

**Q5**: Why does this code not make sense?

**A**: As stated in Advanced R

The first element of a call is always the function that gets called.

Let’s see what happens when we run the code

```
x <- expr(foo(x = 1))
x
#> foo(x = 1)
names(x) <- c("x", "")
x
#> foo(1)
names(x) <- c("", "x")
x
#> foo(x = 1)
```

So, giving the first element a name just adds metadata that R ignores.

**Q6**: Construct the expression `if(x > 1) "a" else "b"`

using multiple calls to `call2()`

. How does the code structure reflect the structure of the AST?

**A**: Similar to the prefix version we get

When we read the AST from left to right, we get the same structure: Function to evaluate, expression, which is another function and is evaluated first, and two constants which will be evaluated next.

```
ast(`if`(x > 1, "a", "b"))
#> █─`if`
#> ├─█─`>`
#> │ ├─x
#> │ └─1
#> ├─"a"
#> └─"b"
```

## 14.3 Parsing and grammar

**Q1**: R uses parentheses in two slightly different ways as illustrated by these two calls:

```
f((1))
`(`(1 + 1)
```

Compare and contrast the two uses by referencing the AST.

**A**: The trick with these examples lies in the fact, that `(`

can be a part of R’s general prefix function syntax but can also represent a call to the `(`

function.

So, in the AST of the first example, we will not see the outer `(`

since it is prefix function syntax and belongs to `f()`

. In contrast, the inner `(`

is a function (represented as a symbol in the AST):

```
ast(f((1)))
#> █─f
#> └─█─`(`
#> └─1
```

In the second example, we can see that the outer `(`

is a function and the inner `(`

belongs to its syntax:

```
ast(`(`(1 + 1))
#> █─`(`
#> └─█─`+`
#> ├─1
#> └─1
```

For the sake of clarity, let’s also create a third example, where none of the `(`

is part of another function’s syntax:

```
ast(((1 + 1)))
#> █─`(`
#> └─█─`(`
#> └─█─`+`
#> ├─1
#> └─1
```

**Q2**: `=`

can also be used in two ways. Construct a simple example that shows both uses.

**A**: `=`

is used both for assignment, and for naming arguments in function calls:

`b = c(c = 1)`

So, when we play with `ast()`

, we can directly see that the following is not possible:

We get an error because `b =`

makes R looking for an argument called `b`

. Since `x`

is the only argument of `ast()`

, we get an error.

The easiest way around this problem is to wrap this line in `{}`

.

When we ignore the braces and compare the trees, we can see, that the first `=`

is used for assignment and the second `=`

is part of the syntax of function calls.

**Q3**: Does `-2^2`

yield 4 or -4? Why?

**A**: It yields `-4`

, because `^`

has a higher operator precedence than `-`

, which we can verify by looking at the AST (or looking it up under `?"Syntax"`

):

```
-2^2
#> [1] -4
ast(-2^2)
#> █─`-`
#> └─█─`^`
#> ├─2
#> └─2
```

**Q4**: What does `!1 + !1`

return? Why?

**A**: The answer is a little surprising:

```
!1 + !1
#> [1] FALSE
```

To answer the “why?” we take a look at the AST:

```
ast(!1 + !1)
#> █─`!`
#> └─█─`+`
#> ├─1
#> └─█─`!`
#> └─1
```

The right `!1`

is evaluated first. It evaluates to `FALSE`

, because R coerces every non 0 numeric to `TRUE`

, when a logical operator is applied. The negation of `TRUE`

then equals `FALSE`

.

Next `1 + FALSE`

is evaluated to `1`

, since `FALSE`

is coerced to `0`

.

Finally `!1`

is evaluated to `FALSE`

.

Note that if `!`

had a higher precedence, the intermediate result would be `FALSE + FALSE`

, which would evaluate to `0`

.

**Q5**: Why does `x1 <- x2 <- x3 <- 0`

work? Describe the two reasons.

**A**: One reason is that `<-`

is right-associative, i.e. evaluation takes place from right to left:

`x1 <- (x2 <- (x3 <- 0))`

The other reason is that `<-`

invisibly returns the value on the right-hand side.

```
(x3 <- 0)
#> [1] 0
```

**Q6**: Compare the ASTs of `x + y %+% z`

and `x ^ y %+% z`

. What have you learned about the precedence of custom infix functions?

**A**: Let’s take a look at the syntax trees:

```
ast(x + y %+% z)
#> █─`+`
#> ├─x
#> └─█─`%+%`
#> ├─y
#> └─z
```

Here `y %+% z`

will be calculated first and the result will be added to `x`

.

```
ast(x ^ y %+% z)
#> █─`%+%`
#> ├─█─`^`
#> │ ├─x
#> │ └─y
#> └─z
```

Here `x ^ y`

will be calculated first, and the result will be used as first argument to `%+%()`

.

We can conclude that custom infix functions have precedence between addition and exponentiation.

The exact precedence of infix functions can be looked up under `?"Syntax"`

where we see that it lies directly behind the sequence operator (`:`

) and in front of the multiplication and division operators (`*`

and `/`

).

**Q7**: What happens if you call `parse_expr()`

with a string that generates multiple expressions, e.g. `parse_expr("x + 1; y + 1")`

?

**A**: In this case `parse_expr()`

notices that more than one expression would have to be generated and throws an error.

```
parse_expr("x + 1; y + 1")
#> Error: More than one expression parsed
```

**Q8**: What happens if you attempt to parse an invalid expression, e.g. `"a +"`

or `"f())"`

?

**A**: Invalid expressions will lead to an error in the underlying `parse()`

function.

```
parse_expr("a +")
#> Error in parse(text = elt): <text>:2:0: unexpected end of input
#> 1: a +
#> ^
parse_expr("f())")
#> Error in parse(text = elt): <text>:1:4: unexpected ')'
#> 1: f())
#> ^
parse(text = "a +")
#> Error in parse(text = "a +"): <text>:2:0: unexpected end of input
#> 1: a +
#> ^
parse(text = "f())")
#> Error in parse(text = "f())"): <text>:1:4: unexpected ')'
#> 1: f())
#> ^
```

**Q9**: `deparse()`

produces vectors when the input is long. For example, the following call produces a vector of length two:

```
expr <- expr(g(a + b + c + d + e + f + g + h + i + j + k + l + m +
n + o + p + q + r + s + t + u + v + w + x + y + z))
deparse(expr)
```

What does `expr_text()`

do instead?

**A**: `expr_text()`

will paste the results from `deparse(expr)`

together and use a linebreak (`\n`

) as separator.

```
expr <- expr(g(a + b + c + d + e + f + g + h + i + j + k + l + m +
n + o + p + q + r + s + t + u + v + w + x + y + z))
deparse(expr)
#> [1] "g(a + b + c + d + e + f + g + h + i + j + k + l + m + n + "
#> [2] "o + p + q + r + s + t + u + v + w + x + y + z)"
expr_text(expr)
#> [1] "g(a + b + c + d + e + f + g + h + i + j + k + l + m + n
#> + \n o + p + q + r + s + t + u + v + w + x + y + z)"
```

**Q10**: `pairwise.t.test()`

assumes that `deparse()`

always returns a length one character vector. Can you construct an input that violates this expectation? What happens?

**A**: The function `pairwise.t.test()`

captures its data arguments (`x`

and `g`

) so it can print the input expressions along the computed p-values. Prior to R 4.0.0 this used to be implemented via `deparse(subsitute(x))`

in combination with `paste()`

. This could lead to unexpected output, if one of the inputs exceeded the default `width.cutoff`

value of 60 characters within `deparse()`

. In this case, the expression would be split into a character vector of length greater 1.

```
# Output in R version 3.6.2
d <- 1
pairwise.t.test(2, d + d + d + d + d + d + d + d +
d + d + d + d + d + d + d + d + d)
#> Pairwise comparisons using t tests with pooled SD
#>
#> data: 2 and d + d + d + d + d + d + d + d + d + d + d + d + d + d
#> + d + d + 2 and d
#>
#> <0 x 0 matrix>
#>
#> P value adjustment method: holm
```

In R 4.0.0 `pairwise.t.test()`

was updated to use the newly introduced `deparse1()`

, which serves as a wrapper around `deparse()`

.

deparse1() is a simple utility added in R 4.0.0 to ensure a string result (character vector of length one), typically used in name construction, as deparse1(substitute(.)).

```
# Output since R 4.0.0
d <- 1
pairwise.t.test(2, d + d + d + d + d + d + d + d +
d + d + d + d + d + d + d + d + d)
#> Pairwise comparisons using t tests with pooled SD
#>
#> data: 2 and d + d + d + d + d + d + d + d + d + d + d + d + d + d
#> + d + d + d
#>
#> <0 x 0 matrix>
#>
#> P value adjustment method: holm
```

## 14.4 Walking AST with recursive functions

**Q1**: `logical_abbr()`

returns `TRUE`

for `T(1, 2, 3)`

. How could you modify `logical_abbr_rec()`

so that it ignores function calls that use `T`

or `F`

?

**A**: We can apply a similar logic as in the assignment example from Advanced R. We just treat it as a special case handled within a sub function called `find_T_call()`

, which finds `T()`

calls and “bounces them out.” Therefore, we also repeat the `expr_type()`

helper which tells us if we are in the base or in the recursive case.

```
expr_type <- function(x) {
if (rlang::is_syntactic_literal(x)) {
"constant"
} else if (is.symbol(x)) {
"symbol"
} else if (is.call(x)) {
"call"
} else if (is.pairlist(x)) {
"pairlist"
} else {
typeof(x)
}
}
switch_expr <- function(x, ...) {
switch(expr_type(x),
...,
stop("Don't know how to handle type ",
typeof(x), call. = FALSE))
}
```

```
find_T_call <- function(x) {
if (is_call(x, "T")) {
x <- as.list(x)[-1]
purrr::some(x, logical_abbr_rec)
} else {
purrr::some(x, logical_abbr_rec)
}
}
logical_abbr_rec <- function(x) {
switch_expr(
x,
# Base cases
constant = FALSE,
symbol = as_string(x) %in% c("F", "T"),
# Recursive cases
pairlist = purrr::some(x, logical_abbr_rec),
call = find_T_call(x)
)
}
logical_abbr <- function(x) {
logical_abbr_rec(enexpr(x))
}
```

Now let’s test our new `logical_abbr()`

function:

```
logical_abbr(T(1, 2, 3))
#> [1] FALSE
logical_abbr(T(T, T(3, 4)))
#> [1] TRUE
logical_abbr(T(T))
#> [1] TRUE
logical_abbr(T())
#> [1] FALSE
logical_abbr()
#> [1] FALSE
logical_abbr(c(T, T, T))
#> [1] TRUE
```

**Q2**: `logical_abbr()`

works with expressions. It currently fails when you give it a function. Why? How could you modify `logical_abbr()`

to make it work? What components of a function will you need to recurse over?

```
f <- function(x = TRUE) {
g(x + T)
}
```

**A**: The function currently fails, because `"closure"`

is not handled in `switch_expr()`

within `logical_abbr_rec()`

.

```
logical_abbr(!!f)
#> Error: Don't know how to handle type closure
```

If we want to make it work, we have to write a function to also iterate over the formals and the body of the input function.

**Q3**: Modify `find_assign`

to also detect assignment using replacement functions, i.e. `names(x) <- y`

.

**A**: Let`s see what the AST of such an assignment looks like:

So, we need to catch the case where the first two elements are both calls. Further the first call is identical to `<-`

and we must return only the second call to see which objects got new values assigned.

This is why we add the following block within another `else`

statement in `find_assign_call()`

:

Let us finish with the whole code, followed by some tests for our new function:

```
flat_map_chr <- function(.x, .f, ...) {
purrr::flatten_chr(purrr::map(.x, .f, ...))
}
find_assign <- function(x) unique(find_assign_rec(enexpr(x)))
find_assign_call <- function(x) {
if (is_call(x, "<-") && is_symbol(x[[2]])) {
lhs <- as_string(x[[2]])
children <- as.list(x)[-1]
} else {
if (is_call(x, "<-") && is_call(x[[2]])) {
lhs <- expr_text(x[[2]])
children <- as.list(x)[-1]
} else {
lhs <- character()
children <- as.list(x)
}}
c(lhs, flat_map_chr(children, find_assign_rec))
}
find_assign_rec <- function(x) {
switch_expr(
x,
# Base cases
constant = ,symbol = character(),
# Recursive cases
pairlist = flat_map_chr(x, find_assign_rec),
call = find_assign_call(x)
)
}
# Tests functionality
find_assign(x <- y)
#> [1] "x"
find_assign(names(x))
#> character(0)
find_assign(names(x) <- y)
#> [1] "names(x)"
find_assign(names(x(y)) <- y)
#> [1] "names(x(y))"
find_assign(names(x(y)) <- y <- z)
#> [1] "names(x(y))" "y"
```

**Q4**: Write a function that extracts all calls to a specified function.

**A**: Here we need to delete the previously added else statement and check for a call (not necessarily `<-`

) within the first `if()`

in `find_assign_call()`

. We save a call when we found one and return it later as part of our character output. Everything else stays the same:

```
find_assign_call <- function(x) {
if (is_call(x)) {
lhs <- expr_text(x)
children <- as.list(x)[-1]
} else {
lhs <- character()
children <- as.list(x)
}
c(lhs, flat_map_chr(children, find_assign_rec))
}
find_assign_rec <- function(x) {
switch_expr(
x,
# Base cases
constant = ,
symbol = character(),
# Recursive cases
pairlist = flat_map_chr(x, find_assign_rec),
call = find_assign_call(x)
)
}
find_assign(x <- y)
#> [1] "x <- y"
find_assign(names(x(y)) <- y <- z)
#> [1] "names(x(y)) <- y <- z" "names(x(y))" "x(y)"
#> [4] "y <- z"
find_assign(mean(sum(1:3)))
#> [1] "mean(sum(1:3))" "sum(1:3)" "1:3"
```