anchor.diff:  
   === Using immutable class instances for persistence
   
  -In Kotlin, it is very convenient and a best practice to declare read-only properties within
  -the primary constructor, as in the following example:
  +In Kotlin, it is very convenient and considered best practice to declare
  +read-only properties within the primary constructor, as in the following
  +example:
   
   [source,kotlin]
   ----
  
positive.code: Kotlin provides similar support and allows the rendering of Kotlin based templates, see
  https://github.com/spring-projects/spring-framework/commit/badde3a479a53e1dd0777dd1bd5b55cb1021cf9e[this commit] for details.
  
  This enables some interesting use cases like writing type-safe templates using
  https://github.com/Kotlin/kotlinx.html[kotlinx.html] DSL or simply using Kotlin multiline `String` with interpolation.
  
  This can allow one to write Kotlin templates with full autocompletion and
  
negative.code: ----
  
  As in Java, `users` in Kotlin is strongly typed, but Kotlin's clever type inference allows
  for shorter syntax.
  
  [[null-safety]]
  == Null-safety
  
  One of Kotlin's key features is https://kotlinlang.org/docs/reference/null-safety.html[null-safety]
  - which cleanly deals with `null` values at compile time rather than bumping into the famous
  `NullPointerException` at runtime. This makes applications safer through nullability
  declarations and expressing "value or no value" semantics without paying the cost of wrappers like `Optional`.
  (Kotlin allows using functional constructs with nullable values; check out this
  