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
reduce false positives of tail-expr-drop-order from consumed values
take 2
open up coroutines
tweak the wordings
the lint works up until 2021
We were missing one case, for ADTs, which was
causing `Result` to yield incorrect results.
only include field spans with significant types
deduplicate and eliminate field spans
switch to emit spans to impl Drops
Co-authored-by: Niko Matsakis <nikomat@amazon.com>
collect drops instead of taking liveness diff
apply some suggestions and add explantory notes
small fix on the cache
let the query recurse through coroutine
new suggestion format with extracted variable name
fine-tune the drop span and messages
bugfix on runtime borrows
tweak message wording
filter out ecosystem types earlier
apply suggestions
clippy
check lint level at session level
further restrict applicability of the lint
translate bid into nop for stable mir
detect cycle in type structure
using `.deref()` on a double reference, which returns `{$ty}` instead of dereferencing the inner type
774
774
775
-
lint_tail_expr_drop_order = these values and local bindings have significant drop implementation that will have a different drop order from that of Edition 2021
776
-
.label = these values have significant drop implementation and will observe changes in drop order under Edition 2024
777
-
778
775
lint_trailing_semi_macro = trailing semicolon in macro used in expression position
779
776
.note1 = macro invocations at the end of a block are treated as expressions
780
777
.note2 = to ignore the value produced by the macro, add a semicolon after the invocation of `{$name}`
0 commit comments