anchor.diff:  
   Note that while our `PointList` class has numerous list methods available
   (`size`, `contains`, `forEach`, `stream`, etc.) courtesy of Groovy's `@Delegate` transform,
  -these are baked into the class file, not calling into any Groovy library or runtime code.
  +these are baked into the class file, and the bytecode produced doesn't call
  +into any Groovy libraries or rely on any runtime code.
   
   When run, the following output is produced:
   
  
positive.code: in situations where Java might become confused by Groovy's "plumbing" methods.
  
  The feature is incubating. Currently, the presence of the annotation should be
  treated like a hint to the compiler to produce bytecode not relying on the Groovy runtime
  if it can but not a guarantee. Users of `@CompileStatic` will know that certain dynamic
  features aren't possible when they switch to static Groovy.
  Even so, while the desire is to produce Java-like code,
  there are numerous Groovy feature which still work for some scenarios.
  
  Consider the following example. First a Groovy `Point` class:
  
  
negative.code: This feature is used in numerous places within the Groovy codebase for testing purposes.
  Various code snippets are compiled using both Java and Groovy to ensure the compiler is behaving as intended.
  We also use this feature to provide a productivity enhancement for polyglot developers allowing
  Java code to be compiled and/or run (as Java) from within the Groovy Console:
  
  image:img/groovyconsole_run_as_java.png[image] +
  
  