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
{{ message }}
This repository was archived by the owner on May 28, 2025. It is now read-only.
Auto merge of rust-lang#3802 - RalfJung:no-more-call-id, r=RalfJung
Borrow tracking: remove the concept of a call ID
Turns out this is not needed any more ever since we started tracking the `protected_tags` list in the per-frame state.
Also thanks to `@JoJoDeveloping` for inspiring me to even consider this possibility. :)
Copy file name to clipboardExpand all lines: src/tools/miri/tests/fail/both_borrows/aliasing_mut1.stack.stderr
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
error: Undefined Behavior: not granting access to tag <TAG> because that would remove [Unique for <TAG>] which is strongly protected because it is an argument of call ID
1
+
error: Undefined Behavior: not granting access to tag <TAG> because that would remove [Unique for <TAG>] which is strongly protected
2
2
--> $DIR/aliasing_mut1.rs:LL:CC
3
3
|
4
4
LL | pub fn safe(x: &mut i32, y: &mut i32) {
5
-
| ^ not granting access to tag <TAG> because that would remove [Unique for <TAG>] which is strongly protected because it is an argument of call ID
5
+
| ^ not granting access to tag <TAG> because that would remove [Unique for <TAG>] which is strongly protected
6
6
|
7
7
= help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
8
8
= help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
0 commit comments