anchor.diff:  
   == Java syntax
   
  -Constraints written in Java with ConstraintStreams follow the Java Language Specification (JLS), for good or bad.
  -Similar logic applies when using ConstraintStreams from Kotlin or Scala.
  +Constraints written in Java with Constraint Streams follow the Java Language Specification (JLS), for good or bad.
  +Similar logic applies when using Constraint Streams from Kotlin or Scala.
   
   When migrating between DRL and Constraint Streams, be aware of some differences between DRL and Java:
   
  
positive.code: 
  If you're familiar with SQL or Java 8 streams, this should look familiar.
  Given a potential solution with four shifts (two of which are assigned to `Ann`),
  those shifts through it flow like this:
  
  image::constraintStreamFilter_part.png[]
  
  
negative.code: == Incremental calculation
  
  First off, unlike an `EasyScoreCalculator`,
  Constraint Streams still apply incremental score calculation to scale out, just like DRL.
  For example, when a move swaps the employee of two shifts, only the delta is calculated.
  That's a huge scalability gain:
  
  