Improve dangerous_implicit_aurorefs diagnostic output - #140768
Conversation
|
Not a good reviewer for this, maybe r? @RalfJung |
commented
May 8, 2025
|
I'm not really an expert for lint implementations, and hardly use these HIR APIs. Let's see if this works |
e4fac05 to
5e5cacd
Compare
commented
May 14, 2025
|
r? fmease |
This comment was marked as resolved.
This comment was marked as resolved.
5e5cacd to
9b3abe7
Compare
| lint_implicit_unsafe_autorefs = implicit autoref creates a reference to the dereference of a raw pointer | ||
| .note = creating a reference requires the pointer target to be valid and imposes aliasing requirements | ||
| .raw_ptr = this raw pointer has type `{$raw_ptr_ty}` | ||
| .autoref = autoref is being applied to this expression, resulting in: `{$autoref_ty}` |
There was a problem hiding this comment.
We talked about rephrasing "autoref is being applied" to sth. along the lines of "references to this expression are implicitly created", "references are implicitly applied ...", ...
Is that still something we want to pursue?
There was a problem hiding this comment.
Yeah, I wanted to do that but given that the end result type is not going to have a visible reference I just removed the "autoref" note, and just show the deref one.
commented
May 15, 2025
|
@bors r+ rollup |
commented
May 15, 2025
commented
May 15, 2025
|
🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened. |
This PR greatly improves the
dangerous_implicit_aurorefslint diagnostic output.Kind of related to #140721.
r? @jieyouxu (maybe)