You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here there are several uses of 1, 2, and 3 in different roles, e.g. the value of x, the value of a, and y, while also being used as labels for steps 1, 2, and 3 both in the code and in the graphs. This can complicate the parsing of the code and the graphs.
My suggestion is to initiate x with another value, to avoid clashing with the step labels, e.g.
h<-function(x) {
# 1.a<-4# 2.x+a
}
y<- h(5) # 3.
would change the graph enough so that the binding values are x = 5, a = 4, and y = 9.
The text was updated successfully, but these errors were encountered:
HenrikBengtsson
changed the title
Section 7.4.4 Execution environments: clarify by using, say, h(36) instead of h(1)
Section 7.4.4 Execution environments: clarify by using, say, h(5) instead of h(1)
Oct 22, 2022
In Section 7.4.4 Execution environments, there's:
adv-r/Environments.Rmd
Lines 656 to 663 in dc49c38
Here there are several uses of
1
,2
, and3
in different roles, e.g. the value ofx
, the value ofa
, andy
, while also being used as labels for steps 1, 2, and 3 both in the code and in the graphs. This can complicate the parsing of the code and the graphs.My suggestion is to initiate
x
with another value, to avoid clashing with the step labels, e.g.would change the graph enough so that the binding values are
x = 5
,a = 4
, andy = 9
.The text was updated successfully, but these errors were encountered: