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.
I found
lintr::get_source_expressions()
very slow on the file mentioned on the {cyclocomp} performance issue:gaborcsardi/cyclocomp#25
It looks like a lot of the time is consumed in
xml_parse_data()
so I'm looking for some easy performance wins.Avoiding
ifelse()
seems like a good start. Here's a timing comparison ofmap_token()
on the parse data frame from that file:map_token3()
is implemented here.map_token2()
is closer to the original:So I think we've got an 8x speed-up without much change to readability (IMO readability has improved).