anchor.diff:  === Easy testing Kotlin and JUnit 5
   
   Kotlin allows to specify meaningful test function names betweeen backticks,
  -and as of JUnit 5.0 Kotlin test classes can use `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
  +and as of JUnit 5 Kotlin test classes can use `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
   to enable a single instantiation of test classes which allows to use `@BeforeAll` and `@AfterAll`
   annotations on non-static methods, which is a good fit for Kotlin.
   
  
positive.code: 
  === Classes and member functions final by default
  
  By default, https://discuss.kotlinlang.org/t/classes-final-by-default/166[call classes in Kotlin are `final`].
  The `open` annotation on a class is the opposite of Java's `final`: it allows others to
  inherit from this class. Same for member functions that need to be open to be overridden.
  
  While Kotlin JVM-friendly design is generally a good fit with Spring, this specific point
  can prevent your application to start if not taken in account because Spring beans proxified
  with CGLIB - like `@Configuration` classes - need to be inherited at runtime for technical
  reasons.
  
  Before Kotlin 1.0.6, you needed to add an `open` keyword on each class and their member
  functions of Spring beans proxified with CGLIB like `@Configuration` classes.
  
  Fortunately, Kotlin 1.0.6+ now provides a
  
negative.code: As of version 4.3, Spring Framework provides a
  http://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/servlet/view/script/ScriptTemplateView.html[ScriptTemplateView]
  to render templates using script engines that supports https://www.jcp.org/en/jsr/detail?id=223[JSR-223]
  and Spring Framework 5 go even further by extending this feature to WebFlux and supporting
  https://jira.spring.io/browse/SPR-15064[i18n and nested templates].
  
  Kotlin 1.1 provides such support and allows to render Kotlin based templates, see
  