core: fix distance_range_map.to_range_map

[Castavo]

Without this fix, we can't simulate trains with more than 1 power restriction range.

I added a test case.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.01%. Comparing base (d420d30) to head (62c072a).
Report is 21 commits behind head on dev.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##                dev    #8831    +/-   ##
==========================================
  Coverage     37.01%   37.01%            
+ Complexity     2212     2211     -1     
==========================================
  Files          1254     1255     +1     
  Lines        113938   114240   +302     
  Branches       3189     3182     -7     
==========================================
+ Hits          42177    42290   +113     
- Misses        69864    70059   +195     
+ Partials       1897     1891     -6     

Flag	Coverage Δ
core	74.84% <100.00%> (+0.04%)	⬆️
editoast	72.42% <ø> (+<0.01%)	⬆️
front	14.89% <ø> (-0.05%)	⬇️
gateway	2.20% <ø> (ø)
osrdyne	2.71% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	86.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bougue-pe]

Thanks for the test too!

[eckter]

Oof. I was almost certain that building with closed intervals worked, with the old value being overwritten at the transition. I don't know if it was changed but it's kind of bad that we didn't notice it.

Though there's technically no value at the very end with this change. But I don't think it matters.

[Castavo]

@eckter I believe the overwriting works when using a MutableRangeMap rather than an ImmutableRangeMap

[Erashin]

Yay :)