insightsengineering / insightsengineering/teal.code
[Bug]: Iterator of the for loop is treated as an object in get_code_dependency
- Vorherrschende Sprache
- R
- Sterne
- 12
- Forks
- 11
- Ø Merge
- 1 T. 17 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
If object is treated as an iterator in a `for` loop, like `x` below, then `get_code` treats this case as this object created in this `for` loop, hence even though it's a temporary object (just for the time of the `for` loop execution) it gets extracted in the `get_code`
``` r
library(teal.code)
q <- within(qenv(), {
a <- 1
b <- 2
}) |> within({
for (x in c(1, 2)) {
b <- a
b <- b + a + 1
b + 3 -> b
}
}) |> within({
x <- 5
})
get_code(q, names = 'x') |> cat()
#> a <- 1
#> b <- 2
#> for (x in c(1, 2)) {
#> b <- a
#> b <- b + a + 1
#> b <- b + 3
#> }
#> x <- 5
```
Created on 2024-11-27 with [reprex v2.1.1](https://reprex.tidyverse.org)
Beitragsleitfaden
Rechercherichtung
Reproduce the reported R example and start at the get_code_dependency/get_code entry points mentioned in the report. Trace how the for-loop iterator x is recorded as a dependency, then verify that get_code(q, names = 'x') no longer extracts the temporary loop object while retaining x <- 5.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- r
- Bereich
- tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100