rust/tests/ui/static/raw-ref-deref-without-unsafe.stderr

error[E0133]: use of mutable static is unsafe and requires unsafe function or block
  --> $DIR/raw-ref-deref-without-unsafe.rs:10:57
   |
LL | static mut DEREF_BYTE_PTR: *mut u8 = ptr::addr_of_mut!(*BYTE_PTR);
   |                                                         ^^^^^^^^ use of mutable static
   |
   = note: mutable statics can be mutated by multiple threads: aliasing violations or data races will cause undefined behavior

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0133`.
compiler: treat `&raw (const\|mut) UNSAFE_STATIC` implied deref as safe The implied deref to statics introduced by HIR->THIR lowering is only used to create place expressions, it lacks unsafe semantics. It is also confusing, as there is no visible `*ident` in the source. For both classes of "unsafe static" (extern static and static mut) allow this operation. We lack a clear story around `thread_local! { static mut }`, which is actually its own category of item that reuses the static syntax but has its own rules. It's possible they should be similarly included, but in the absence of a good reason one way or another, we do not bless it. 2024-05-31 20:48:42 -05:00			`error[E0133]: use of mutable static is unsafe and requires unsafe function or block`
stabilize const_mut_refs 2024-08-17 07:19:34 -05:00			`--> $DIR/raw-ref-deref-without-unsafe.rs:10:57`
compiler: treat `&raw (const\|mut) UNSAFE_STATIC` implied deref as safe The implied deref to statics introduced by HIR->THIR lowering is only used to create place expressions, it lacks unsafe semantics. It is also confusing, as there is no visible `*ident` in the source. For both classes of "unsafe static" (extern static and static mut) allow this operation. We lack a clear story around `thread_local! { static mut }`, which is actually its own category of item that reuses the static syntax but has its own rules. It's possible they should be similarly included, but in the absence of a good reason one way or another, we do not bless it. 2024-05-31 20:48:42 -05:00			`\|`
			`LL \| static mut DEREF_BYTE_PTR: mut u8 = ptr::addr_of_mut!(BYTE_PTR);`
			`\| ^^^^^^^^ use of mutable static`
			`\|`
			`= note: mutable statics can be mutated by multiple threads: aliasing violations or data races will cause undefined behavior`

A raw ref of a deref is always safe 2024-08-17 12:03:27 -05:00			`error: aborting due to 1 previous error`
compiler: treat `&raw (const\|mut) UNSAFE_STATIC` implied deref as safe The implied deref to statics introduced by HIR->THIR lowering is only used to create place expressions, it lacks unsafe semantics. It is also confusing, as there is no visible `*ident` in the source. For both classes of "unsafe static" (extern static and static mut) allow this operation. We lack a clear story around `thread_local! { static mut }`, which is actually its own category of item that reuses the static syntax but has its own rules. It's possible they should be similarly included, but in the absence of a good reason one way or another, we do not bless it. 2024-05-31 20:48:42 -05:00
			For more information about this error, try `rustc --explain E0133`.