-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Split elided_lifetime_in_paths into finer-grained lints #120808
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
base: master
Are you sure you want to change the base?
Changes from all commits
615e373
f372f1f
e9db3c7
96d0406
6a76e20
4e645f4
10448cc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -292,7 +292,11 @@ lint_hidden_glob_reexport = private item shadows public glob re-export | |||||
.note_glob_reexport = the name `{$name}` in the {$namespace} namespace is supposed to be publicly re-exported here | ||||||
.note_private_item = but the private item here shadows it | ||||||
lint_hidden_lifetime_parameters = hidden lifetime parameters in types are deprecated | ||||||
lint_hidden_lifetime_in_path = | ||||||
paths containing hidden lifetime parameters are deprecated | ||||||
lint_hidden_lifetime_in_path_suggestion = | ||||||
indicate the anonymous lifetime | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
I'd probably say "inferred" here for a couple reasons. One, I'm planning to update the Reference to call this the inferred lifetime (as we call |
||||||
lint_hidden_unicode_codepoints = unicode codepoint changing visible direction of text present in {$label} | ||||||
.label = this {$label} contains {$count -> | ||||||
|
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.
Suggestion [WORDING-STRENGTH 1/2]: I think I agree with @tmandry's comment earlier
where if this set of 3 lints are initially allow-by-default in this PR, we should not use "deprecated" in this PR, but instead add "deprecated" in the follow-up PR that bumps these three lints and the
hidden_lifetimes_in_paths
to warn-by-default, so that the deprecation is part of the follow-up decision to explicitly deprecate this form.In this PR, I would reword this less strong initially, maybe something like
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're still staying "deprecated" here. While at some level I do think that's correct, I'd highlight the comment by @tmandry that @jieyouxu highlighted above; there'd need to be a reply to this to argue for why it should be kept. We would almost certainly get pushback on this language.