anchor.diff:  }
   ----
   
  -Anonymous function call and object constructor call can be banged too :
  +In the previous listing, the `hello!(name)` in the loop is considered the same
  +call, and thus evaluated only on the first iteration. On the other hand, the
  +previous calls with `"Foo"` and `"Bar"` are distinct, and therefore prints
  +different results.
  +
  +
  +Anonymous function call and object constructor call can be banged too:
   
   [source,golo]
   ----
  
positive.code: 
  In this example `take_a_while` is computed only once at the first call, and then this function returns directly the previously computed result as a constant for every subsequent call.
  
  
  Bang function call is a kind of memoization but regardless the given parameters :
  
  [source,golo]
  ----
  
negative.code: }
  ----
  
  In this example `hello` is executed at the first call with the parameter
  `"Peter"`, then always returns `"Hello Peter!"`, even when called with other
  values.
  
  WARNING: Functions having side effects *should* not be marked, since the computation
  is not done for subsequent calls, and thus the side effect can't happen. In the
  same way, function that depends on an outside context are risky. Indeed, a
  change in the context won't imply a change in the result any more. In other
  words, only _pure_ functions should be marked with a `!`. No check are done by
  the language, use it at your own risk.
  
  The result of a banged function call is constant within the same call place,
  but different for each call instructions.
  
  [source,golo]
  ----
  