Side effect (computer science)
In computer science, an operation or expression is said to have a side effect if it has any observable effect other than its primary effect of reading the value of its arguments and returning a value to the invoker of the operation. Example side effects include modifying a non-local variable, a static local variable or a mutable argument passed by reference; performing I/O; or calling other functions with side-effects. In the presence of side effects, a program's behaviour may depend on history; that is, the order of evaluation matters. Understanding and debugging a function with side effects requires knowledge about the context and its possible histories.
From Wikipedia, the free encyclopedia "Hidden side effect" redirects here. For similar uses, see Hidden variable. In computer science, an operation or expression is said to have a side effect if it has any observable effect other than its primary effect of reading the value of its arguments and returning a value to the invoker of the operation. Example side effects include modifying a non-local variable, a static local variable or a mutable argument passed by reference; performing I/O; or calling other functions with side-effects.[1] In the presence of side effects, a program's behaviour…
saved by
related reading
- Seven Implementations of Incremental :: Jane Streetjanestreet.com
- CSAPP_2016.pdfcs.sfu.ca
- Effect system - Wikipediaen.wikipedia.org
- how I think when I think about programming - alice mazalicemaz.com
- Algebraic Effects for the Rest of Us — overreactedoverreacted.io
- Learnable Programmingworrydream.com
- A practical introduction to functional programmingmaryrosecook.com
- state - Advantages of stateless programming? - Stack Overflowstackoverflow.com
- Modal Effect Typesarxiv.org
- Out of the Tar Pitcurtclifton.net
- Stephen Wolfram Writingswritings.stephenwolfram.com
- An introduction to functional programmingcodewords.recurse.com