Skip to content

Dropped Range from the TrackBestTrackCreator input

Sebastien Ponce requested to merge TrackBestTrackNoRange into future

Range cannot be used so easily as their is a constness discrepency between the iterators from the KeyedContainer and the ones needed by the Range. This is asking for a major review of the Range and Container code but for the moment, I've dropped the Range usage, and that make mini Brunel happy :-)

Merge request reports