Data parsing fixes#450
Merged
Merged
Conversation
Owner
|
retrigger-benchmark |
|
⏱️ Benchmark run finished in 2m 3s 📈 Compared against baseline: 124s 🟢 Generation time is unchanged. You can retrigger the benchmark by commenting |
Owner
|
retrigger-benchmark |
Owner
|
LGTM, thanks a lot! :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
parse_osm_datatake ownership of the raw data instead of the caller cloning it. IOW, the parser function transmutes the raw data to the parsed stuff.SplitOsmDatanow does the work of splitting the elements by type, so the loops that handle them don't need to check for types themselves (and also can work without references, on the data itself.) (Future work could improve things there for less cloning.)