Uh oh!
There was an error while loading. Please reload this page.
HgVertex cleanup/speedup; LABEL_INVALID_CHAR fixes - #416
Merged
Conversation
flag once per label; note UTF-8 BOM cases interactive rebase 9197da3
yakra
commented
Feb 16, 2021
ContributorAuthor
Might have one more commit to add on to this. |
jteresco
commented
Feb 17, 2021
Contributor
bring in? |
yakra
commented
Feb 17, 2021
ContributorAuthor
Ready to bring in. I'll save that commit for later. |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
first_waypointvariable.lat&lngorfirst_waypointfrom HGVertex, but not both. 315f834 removesfirst_waypoint. This option takes up about 4 MB more RAM, but the other option is slightly slower and requires minor changes toPlaceRadius.