This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
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.
Done, but do not merge yet: Async/Await syntax. #600
Done, but do not merge yet: Async/Await syntax. #600
Changes from all commits
21c01e6
5995738
454d5b6
686fa53
5c91bc4
03db389
9e711a4
d0b7cb1
0283e8d
dc85c21
66defd5
ff69dfa
3d5af74
702d586
046d1e3
41844e6
fcd3c32
d20b149
3b17a08
bff364e
c15dee0
5e9b914
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a lot of these. Should there be a generic concept of which this is an instance so all these calls are moved to a single place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give an example of what you mean by this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can move to a helper function, though the difference is minimal. Just easier to make sure all the instances are updated at once if something changes in future.
Another thing I was wondering is: this case seems to often go where there is also
ParsetreeViewer.filterParsingAttrs attrs
. But not always, so not sure what value this observation has.But I guess in the cases where
ParsetreeViewer.filterParsingAttrs attrs
is checked, this await check could at least go right after it. Assuming that no cases in between should take precedence.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is there a separate case for process attributes?
Why not always process attributes and if nothing of interest is found then it's a no-op.
And the following match case disappears.