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
Auto merge of #131326 - dingxiangfei2009:issue-130836-attempt-2, r=nikomatsakis
Reduce false positives of tail-expr-drop-order from consumed values (attempt #2)
r? `@nikomatsakis`
Tracked by #123739.
Related to #129864 but not replacing, yet.
Related to #130836.
This is an implementation of the approach suggested in the [Zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/temporary.20drop.20order.20changes). A new MIR statement `BackwardsIncompatibleDrop` is added to the MIR syntax. The lint now works by inspecting possibly live move paths before at the `BackwardsIncompatibleDrop` location and the actual drop under the current edition, which should be one before Edition 2024 in practice.
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