summaryrefslogtreecommitdiffstats
path: root/tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:03 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:03 +0000
commit64d98f8ee037282c35007b64c2649055c56af1db (patch)
tree5492bcf97fce41ee1c0b1cc2add283f3e66cdab0 /tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs
parentAdding debian version 1.67.1+dfsg1-1. (diff)
downloadrustc-64d98f8ee037282c35007b64c2649055c56af1db.tar.xz
rustc-64d98f8ee037282c35007b64c2649055c56af1db.zip
Merging upstream version 1.68.2+dfsg1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs')
-rw-r--r--tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs44
1 files changed, 44 insertions, 0 deletions
diff --git a/tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs b/tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs
new file mode 100644
index 000000000..daff037b2
--- /dev/null
+++ b/tests/ui/methods/method-mut-self-modifies-mut-slice-lvalue.rs
@@ -0,0 +1,44 @@
+// run-pass
+// Test that an `&mut self` method, when invoked on a place whose
+// type is `&mut [u8]`, passes in a pointer to the place and not a
+// temporary. Issue #19147.
+
+use std::slice;
+use std::cmp;
+
+trait MyWriter {
+ fn my_write(&mut self, buf: &[u8]) -> Result<(), ()>;
+}
+
+impl<'a> MyWriter for &'a mut [u8] {
+ fn my_write(&mut self, buf: &[u8]) -> Result<(), ()> {
+ let amt = cmp::min(self.len(), buf.len());
+ self[..amt].clone_from_slice(&buf[..amt]);
+
+ let write_len = buf.len();
+ unsafe {
+ *self = slice::from_raw_parts_mut(
+ self.as_mut_ptr().add(write_len),
+ self.len() - write_len
+ );
+ }
+
+ Ok(())
+ }
+}
+
+fn main() {
+ let mut buf = [0; 6];
+
+ {
+ let mut writer: &mut [_] = &mut buf;
+ writer.my_write(&[0, 1, 2]).unwrap();
+ writer.my_write(&[3, 4, 5]).unwrap();
+ }
+
+ // If `my_write` is not modifying `buf` in place, then we will
+ // wind up with `[3, 4, 5, 0, 0, 0]` because the first call to
+ // `my_write()` doesn't update the starting point for the write.
+
+ assert_eq!(buf, [0, 1, 2, 3, 4, 5]);
+}