Turn restriction graph application #6611
Draft
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.
Summary
Do not block intersections with turn restrictions too eagerly when first reaching them from a bad direction.
Fixes #6531
Will make unnecessary to support StreetEdge.turnRestrictions at route time at all, speeding up routing.
Unit tests
There's a test for application of turn restrictions right next to each other which is run in both orders, because it is the situation with most potential for bad logic.
Changelog
The fixed bug is potentially very visible, so this should go to changelog.
Bumping the serialization version id
Yes.
This is a significant change in the graph building.