editoast: make intersection as a type

[woshilapin]

Might help #8794 (comment). And in general, explicit typing is not necessarily bad, just more verbose.

[codecov-commenter]

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

Codecov Report

Attention: Patch coverage is 97.56098% with 1 line in your changes missing coverage. Please review.

Project coverage is 37.19%. Comparing base (a184fb5) to head (dc827c6).
Report is 16 commits behind head on dev.

Files with missing lines	Patch %	Lines
editoast/src/views/path/projection.rs	96.42%	1 Missing ⚠️

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

Additional details and impacted files

@@             Coverage Diff              @@
##                dev    #8897      +/-   ##
============================================
+ Coverage     37.11%   37.19%   +0.08%     
- Complexity     2211     2245      +34     
============================================
  Files          1260     1260              
  Lines        115145   115468     +323     
  Branches       3230     3267      +37     
============================================
+ Hits          42737    42953     +216     
- Misses        70475    70569      +94     
- Partials       1933     1946      +13     

Flag	Coverage Δ
core	74.79% <ø> (+0.12%)	⬆️
editoast	72.59% <97.05%> (+0.02%)	⬆️
front	15.17% <100.00%> (-0.01%)	⬇️
gateway	2.20% <ø> (ø)
osrdyne	2.60% <ø> (ø)
railjson_generator	87.49% <ø> (ø)
tests	86.46% <ø> (ø)

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.

[emersion]

FWIW I think it's completely fine to use tuples in internal editoast APIs. I don't think it's a big deal if we need to convert them before sending them over HTTP.

[woshilapin]

FWIW I think it's completely fine to use tuples in internal editoast APIs. I don't think it's a big deal if we need to convert them before sending them over HTTP.

Well, to me, (u64, u64) doesn't give a clue about what is each integer. But a Intersection { start: u64, end: u64 } does give a hint about what you can expect, and as code, not as comment (so always up-to-date). So I do believe it's often an improvement.

[leovalais]

Nice improvement:)

[flomonster]

LGTM, thanks for this PR