stdcm: only simulate edges up to the next stop #3667
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When computing stdcm edges, we now only go up to the first stop. Before this, we always simulated an envelope over the whole route and sometimes detected invalid conflicts after the end of the path. Fixes a bug reproduced in a couple unit tests that were disabled.
First step for #3301.
To do this, there has been a problem: we sometimes need to simulate a 0-length path. To do this, I have removed the assertion in
EnvelopePart
about single point parts. The alternative would have been a new class implementing an interface shared withEnvelope
, but it would be a heavier change. I'd like feedback on this.