anchor.diff:  The JSR 305 checks can be configured by adding the `-Xjsr305` compiler flag with the following
   options: `-Xjsr305={strict|warn|ignore}`.
   
  -For kotlin versions 1.1.50+, the default behavior is the same to `-Xjsr305=warn`. The
  -`strict` value should be considered experimental (Spring API nullability declaration could
  -evolve even between minor releases and more checks may be added in the future).
  +For kotlin versions 1.1.50+, the default behavior is the same to `-Xjsr305=warn`.
  +The `strict` value is required to have Spring Framework API full null-safety taken in account
  +but should be considered experimental since Spring API nullability declaration could evolve
  +even between minor releases and more checks may be added in the future).
   
   [NOTE]
   ====
  
positive.code: }
  ----
  
  [[getting-started]]
  == Getting started
  
  
negative.code: https://youtrack.jetbrains.com/issue/KT-11235[this Kotlin language design issue].
  
  === Testing
  
  ==== Per class lifecycle
  
  Kotlin allows one to specify meaningful test function names between backticks,
  and as of JUnit 5 Kotlin test classes can use the `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
  