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.
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
Make
ARG002
compatible withEM101
when raisingNotImplementedError
#13714Make
ARG002
compatible withEM101
when raisingNotImplementedError
#13714Changes from 1 commit
9d698ac
37c2359
a926d88
b929574
0f9ee12
c5e1b4a
62650d8
168e631
488a407
5bb9729
e92ccf4
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.
Nit:
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.
I see mixed usages of
&**
andas_ref
throughout the code base. Out of curiosity, when is one used over the other? The general heuristic I've seen is*
and&
are recommended for simple stuff; and, once you start de-referencing and re-borrowing, thatas_ref
is recommended if just to avoid needing to think about whatever container the value* is in.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.
We used to use
as_ref
but started to prefer dereferencing (except forOption
where you still needas_ref
andas_deref
) because it's possible thatas_ref
becomes ambiguous if a newAsRef
implementation is added to a type. For example,String
has manyas_ref
methods: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.
Oh interesting, that makes sense! Thank you!