title: Side Effects in R programming the walk() function
body: <p>I'm sure my question seems a little basic, but somehow I am not able to understand the concept of how the Walk() function prevents the side effects.<br>
  Lets say in the example:</p>
  
  <pre><code>x (1,"a",3)
  print(x) 
  </code></pre>
  
  <p>would lead do a side effect the prints the value in the console and changes the environment. Now to avoid this we substitute it with the walk function under the purr package by  x %>% walk(print) to avoid this but still the values are displayed in the console, isn't this a side effect ?<br>
  How would this be different?<br>
  Moreover we can use the walk2 function and iterate the function over a set of arguments and providing a set of results. Now this would somewhere change the state of the system how is this not a side effect? </p>
  
  <p>So my underlying doubt is how does the walk() function avoid side effects successfully </p>