Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-2478

Consecutive Intervals Constraint Collector: Javadoc + Seperation of API, Breaks, Performance Improvement

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 8.10.0.Final
    • None
    • optaplanner-core
    • None
    • 2021 Week 28-30 (from Jul 12)
    • 3
    • Undefined
    • NEW
    • NEW

      • The convention in Java is that the start is inclusive, the end is exclusive. (You can check for yourself that JDK functions follow that convention religiously). The Javadocs on the constraint collector static methods need to say that.
      • Ideally also the code would say it - when you're accepting a range in any constructor, just name the variable properly. (endMap, for example, would becomeĀ endMapExclusive.)
      • Support for breaks between consecutive intervals
      • Separation between API and implementation
      • Try to improve performance on remove

              cchianel Christopher Chianelli (Inactive)
              cchianel Christopher Chianelli (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: