You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: Enforce lint rule clippy::needless_pass_by_value to datafusion-catalog (apache#18638)
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes#123` indicates that this PR will close issue #123.
-->
- Closesapache#18609.
## Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->
The type `impl AsRef<str>` is implicitly `Sized`, meaning its size is
known at compile time.
`&(impl AsRef<str>)` is a reference to a concrete type that implements
`AsRef<str>` and is `Sized`. However, this `Sized` bound prevents
passing references to dynamically sized types such as `&str`, `String`,
or `Box<dyn Trait>`.
Therefore, we add `+ ?Sized` to indicate that the referenced type might
not have a fixed size — that is, it allows the referenced type to be
dynamically sized.
## What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->
- Enforce lint rule `clippy::needless_pass_by_value` to
`datafusion-catalog`.
## Are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
Signed-off-by: Alan Tang <jmtangcs@gmail.com>
0 commit comments