anchor.diff:  this is by no means mandatory to not use it if you think it halters the readability of your code.
   
   A word of caution, however. When using methods which are defined with the `def` keyword instead of a specific concrete type,
  -you may be surprise to see the last expression being returned sometimes. So usually prefer using a specific return type like void or a type.
  +you may be surprised to see the last expression being returned sometimes. So usually prefer using a specific return type like void or a type.
   In our example above, imagine we forgot to put m2 as last statement to be returned,
   the last expression would be `m2.c = 3`, which would return... `3`, and not the map you expect.
   
  
positive.code: 
  == Catch any exception
  
  If you don't really care of the exception which are thrown inside your `try` block,
  you can simply catch any of them and simply omit the type of the caught exception.
  So instead of catching the exceptions like in:
  
  
negative.code: String toString() { "a server" }
  ----
  
  But sometimes, this doesn't look too good when you're using a variable, and see it visually twice on two rows:
  
  [source,groovy]
  ----
  