-
-
Notifications
You must be signed in to change notification settings - Fork 1k
chain: drop redundant check
#7095
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
matthewhughes934
wants to merge
1
commit into
rust-lang:main
Choose a base branch
from
matthewhughes934:chain-refactor-2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
The PR description didn't fully help me understand why this is a redundant check. Can you try to explain it differently?
Also, is it fine to just remove the FIXME comment?
View changes since the review
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.
Here's my attempt at rewriting description/commit body to be clearer (trying to TL;DR: previously we would skip rewriting comments here if we were removing
try!expressions because of how spans work. But in fact, we can never have atry!here, so we don't need to worry about it).While processing children in a chain, e.g. the
1.foo.barinroot.1.foo.barthere was a check that would skip handling comments(and so remove them) if the
use_try_shorthandconfig option was set.This is because previously in the processing (trace:
Chain::from_ast->
Chain::make_subexpr_list->Chain::pop_expr_chain) we wouldreplace
try!(..)expressions with?ones but not update spans,making it difficult to recover comment snippets.
However, it's not possible for a
try!macro to appear as a child, e.g.root.try!(bar);. Firstly note thetry!is not a valid identifier,then the possible types of chain are:
MethodCallExpression → Expression . PathExprSegment ( CallParams? )(e.g.
root.some_method()):PathExprSegmentstarts with aPathIdentSegment, starts with aIDENTIFIER:try!cannot be thestart of a
PathExprSegmentso we can't havetry!in a methodchain.
FieldExpression → Expression . IDENTIFIER(e.g.root.sub):try!is not a valid identifier, so we can't have
try!as a fieldexpression
TupleIndexingExpression → Expression . TUPLE_INDEX(e.g.root.0):tuple index is repeated decimal digits:
try!doesn't match.await,.use,.yield:try!doesn'tmatch
Of course a:
try!can be the root of a chaintry!(foo).barisperfectly valid. And
?can be used anywhere in a chain:foo.try!(bar)is invalid, butfoo.bar?is valid. This change onlyfocuses on the
try!macros.